CVE-2022-0381: The Embed Swagger WordPress plugin is vulnerable to Reflected Cross-Site Scripting due to insufficient escapin

Q: How do I fix CVE-2022-0381?

embed swagger: upgrade to newer than 1.0.0. Exact commands for each OS are on this page.

Q: Is CVE-2022-0381 being exploited?

CVE-2022-0381 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-2022-0381 affect?

CVE-2022-0381 affects embed swagger. Severity is medium (CVSS 6.1). The Embed Swagger WordPress plugin is vulnerable to Reflected Cross-Site Scripting due to insufficient escaping/sanitization and validation via the url parameter found in the ~/swagger-iframe.php file which allows attackers to inject arbitr

Q: How urgent is CVE-2022-0381?

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

This month

MEDIUM 6.1UPGRADE

CVE-2022-0381 is a medium-severity flaw (CVSS 6.1) affecting embed swagger. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

The Embed Swagger WordPress plugin is vulnerable to Reflected Cross-Site Scripting due to insufficient escaping/sanitization and validation via the url parameter found in the ~/swagger-iframe.php file which allows attackers to inject arbitrary web scripts onto the page, in versions up to and including 1.0.0.

Why this priority

EPSS top 10%: 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	3.9% (top 10%)
CISA exploited list	No
Weakness	CWE-79
Published	2022-02-04
Last modified	2026-06-17

Publisher (CNA): Wordfence · Vendor: embed swagger project

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

Am I affected?

Timeline

2022-02-04 23:15 UTCPublished CVE record published
2026-06-17 04:20 UTCUpdated Record last modified

embed swagger project embed swagger UPGRADE

Affected: <= 1.0.0

Fixed in: newer than 1.0.0

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy embed-swagger || rpm -q embed-swagger || embed-swagger --version

2. UPGRADE to newer than 1.0.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade embed-swagger

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade embed-swagger

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 Embed Swagger <=1.0.0 - 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-2022-0381?

embed swagger: upgrade to newer than 1.0.0. Exact commands for each OS are on this page.

Is CVE-2022-0381 being exploited?

CVE-2022-0381 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-2022-0381 affect?

CVE-2022-0381 affects embed swagger. Severity is medium (CVSS 6.1). The Embed Swagger WordPress plugin is vulnerable to Reflected Cross-Site Scripting due to insufficient escaping/sanitization and validation via the url parameter found in the ~/swagger-iframe.php file which allows attackers to inject arbitr

How urgent is CVE-2022-0381?

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

Software pages

WordPress vulnerabilities · PHP vulnerabilities

References

← Back to latest CVEs