CVE-2019-16332 — In the api-bearer-auth plugin before 20190907 for WordPress, the server paramete

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.

01What is this 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.

02Affected products

Vendor	Product	Versions
n	a / n/a	n/a

03Active exploitation status

Not currently listed on the CISA Known Exploited Vulnerabilities (KEV) catalog. EPSS is the best forward-looking signal — see the EPSS row above.

04Recommended remediation

• Patch to a fixed version listed in the vendor advisory (see references below).
• Mitigate with WAF rules, network egress filters, or feature flags where the patch is not yet available.
• Hunt historical logs for exploitation indicators — see Detection signatures below.

05Technical details

For the full vendor write-up, exploit chains, and reference implementations, see the references list in section 09.

06Detection signatures

Ask SARA in chat to draft a starting detection for this CVE in your stack of choice.

07Related CVEs

No directly-cited follow-up CVEs in the KB record for this advisory. The references list in section 09 carries the vendor cross-references.

08Timeline

• Published: 2019-09-15T21:00:40.000Z
• Last modified: 2024-08-05T01:10:41.628Z

09References

• wpvulndb.com — https://wpvulndb.com/vulnerabilities/9868
• packetstormsecurity.com — https://packetstormsecurity.com/files/154369/WordPress-API-Bearer-Auth-20181229-…
• plugins.trac.wordpress.org — https://plugins.trac.wordpress.org/changeset/2152730
• wordpress.org — https://wordpress.org/plugins/api-bearer-auth/#developers