CVE-2019-16332: In the api-bearer-auth plugin before 20190907 for WordPress, the server parameter is not correctly filtered in

Q: How do I fix CVE-2019-16332?

api bearer auth: upgrade to 2019-09-07. Exact commands for each OS are on this page.

Q: Is CVE-2019-16332 being exploited?

CVE-2019-16332 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2019-16332 affect?

CVE-2019-16332 affects api bearer auth. Severity is medium (CVSS 6.1). 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.

Q: How urgent is CVE-2019-16332?

Priority 50/100. EPSS top 7%: very likely to be exploited; Public exploit reference

This month

MEDIUM 6.1UPGRADE

CVE-2019-16332 is a medium-severity flaw (CVSS 6.1) affecting api bearer auth. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

EPSS top 7%: very likely to be exploited
Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	6.1 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	5.7% (top 7%)
CISA exploited list	No
Weakness	CWE-79
Published	2019-09-15
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: api bearer auth project

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2019-09-15 22:15 UTCPublished CVE record published
2026-06-17 02:22 UTCUpdated Record last modified

api bearer auth project api bearer auth UPGRADE

Affected: < 2019-09-07

Fixed in: 2019-09-07

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy api-bearer-auth || rpm -q api-bearer-auth || api-bearer-auth --version

2. UPGRADE to 2019-09-07 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade api-bearer-auth

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade api-bearer-auth

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Public exploits and detection

Public code exists for this CVE. Treat unpatched systems as at risk, and only run PoCs in a lab.

Nuclei scan template: WordPress API Bearer Auth <20190907 - Cross-Site Scripting

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2019-16332?

api bearer auth: upgrade to 2019-09-07. Exact commands for each OS are on this page.

Is CVE-2019-16332 being exploited?

CVE-2019-16332 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2019-16332 affect?

CVE-2019-16332 affects api bearer auth. Severity is medium (CVSS 6.1). 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.

How urgent is CVE-2019-16332?

Priority 50/100. EPSS top 7%: very likely to be exploited; Public exploit reference

Software pages

WordPress vulnerabilities · PHP vulnerabilities

References

← Back to latest CVEs