CVE-2021-36686: Cross-site Scripting in yapi-vendor
Summary
CVE-2021-36686: Cross-site Scripting in yapi-vendor. Affects yapi-vendor versions < 1.9.1. No fix is published. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
yapi-vendor is an npm package that is part of the yapi ecosystem. It is used for managing and interacting with APIs. The package allows users to create, edit, and delete APIs through an interface. However, version 1.9.1 of yapi-vendor is vulnerable to a Cross-site Scripting (XSS) attack.
Vulnerability Detail
The vulnerability in yapi-vendor version 1.9.1 allows attackers to execute arbitrary code through the /interface/api edit page. This means that an attacker can inject malicious scripts into the page, which will be executed by the victim's browser. This can lead to various consequences, such as stealing sensitive information, modifying the page content, or performing actions on behalf of the victim.
How To Fix
No fixed version is published for this vulnerability.
Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →
Workaround
There is no known workaround for this vulnerability. It is essential to update to the latest non-vulnerable version of yapi-vendor to mitigate the risk.
Conclusion
In conclusion, yapi-vendor version 1.9.1 is vulnerable to a Cross-site Scripting (XSS) attack. To mitigate this vulnerability, users should update to the latest non-vulnerable version of yapi-vendor. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for yapi-vendor →
FAQ
yapi-vendor is an npm package used for managing and interacting with APIs.
This vulnerability allows attackers to execute arbitrary code, potentially leading to data theft or unauthorized actions.
To fix this vulnerability, update yapi-vendor to the latest non-vulnerable version.
No, there is no known workaround. Updating to the latest version is the recommended solution.
For more information, you can visit the vulnerability details page on the Vulert website: Vulert Scanner
References
Related vulnerabilities
Recent vulnerabilities recorded for yapi-vendor.