CVE-2019-16332
Api Bearer Auth Project Api Bearer Auth vulnerability
In the api-bearer-auth plugin before 20190907 for WordPress, the server parameter is not correctly filtered in the swagger-config.yaml.php file, and it is possible to inject JavaScript code, aka XSS.
Affected products
Api Bearer Auth. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Api Bearer Auth Project Api Bearer Auth runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- packetstormsecurity.com/files/154369/WordPress-API-Bearer-Auth-20181229-Cross-Site-Scripti · Exploit
- plugins.trac.wordpress.org/changeset/2152730 · Third Party Advisory
- wpvulndb.com/vulnerabilities/9868 · Third Party Advisory
- wordpress.org/plugins/api-bearer-auth/#developers
- nvd.nist.gov/vuln/detail/CVE-2019-16332
- cve.org/CVERecord?id=CVE-2019-16332
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.