# CVE-2025-11241: Yoast SEO Premium 25.7-25.9 - Authenticated (Contributor+) Stored Cross-Site Scripting

> Authenticated contributors can inject malicious JavaScript via flawed regex in Yoast SEO Premium, enabling stored XSS attacks against site visitors.

- **Severity:** Medium 6.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Oct 2025
- **Updated:** 3 Oct 2025
- **Also known as:** GHSA-q494-c83w-2xrf

## What is CVE-2025-11241?

CVE-2025-11241 is a medium-severity cross-site scripting vulnerability in Yoast SEO Premium, published on 3 Oct 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Yoast SEO Premium plugin for WordPress is vulnerable to Stored Cross-Site Scripting in versions 25.7 to 25.9 due to a flawed regex used to remove an attribute in post content, which can be abused to inject arbitrary HTML attributes, including JavaScript event handlers. This vulnerability allows a user with Contributor access or higher to create a post containing a malicious JavaScript payload.

Weakness: CWE-80 (Improper Neutralization of Script-Related HTML Tags in a Web Page)

## Which versions are affected by CVE-2025-11241?


## How do I fix CVE-2025-11241?

No fix has been published for CVE-2025-11241 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-11241 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-11241 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-11241 and fix it if it is affected.

What it is: CVE-2025-11241 is a medium-severity cross-site scripting vulnerability in Yoast SEO Premium, published on 3 Oct 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-11241 exists.

Affected product: Yoast SEO Premium. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-11241/ (Markdown: https://insights.sbomify.com/CVE-2025-11241/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-11241
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-11241
- OSV: https://osv.dev/vulnerability/CVE-2025-11241

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-11241/
Summaries are generated and may contain mistakes; the official description above is the record.