# CVE-2025-11191: RealPress < 1.1.0 - Unauthenticated Content Creation/Email Sending via REST

> Unauthenticated attackers can create pages and send emails via REST API due to missing permission checks in the RealPress WordPress plugin.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 31 Oct 2025
- **Updated:** 9 Jan 2026
- **Also known as:** GHSA-7gxx-5pqg-v8f2

## What is CVE-2025-11191?

CVE-2025-11191 is a medium-severity missing authorization vulnerability in Unknown RealPress, published on 31 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The RealPress  WordPress plugin before 1.1.0 registers the REST routes without proper permission checks, allowing the creation of pages and sending of emails from the site.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2025-11191 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-11191 is a medium-severity missing authorization vulnerability in Unknown RealPress, published on 31 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-11191 exists.

Affected product: Unknown RealPress. 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-11191/ (Markdown: https://insights.sbomify.com/CVE-2025-11191/index.md)
```

## Sources

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

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