# CVE-2025-13307: Ocean Modal Window < 2.3.3 - Editor+ Remote Code Execution via Modal Conditions

> Editors can achieve remote code execution by injecting malicious code into modal display conditions executed via eval.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Dec 2025
- **Updated:** 19 Dec 2025
- **Also known as:** GHSA-7vhr-jxp7-33h3

## What is CVE-2025-13307?

CVE-2025-13307 is a high-severity code injection vulnerability in Unknown Ocean Modal Window, published on 19 Dec 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The Ocean Modal Window WordPress plugin before 2.3.3 is vulnerable to Remote Code Execution via the modal display logic. These modals can be displayed under user-controlled conditions that Editors and Administrators can set (edit_pages capability). The conditions are then executed as part of an eval statement executed on every site page. This leads to remote code execution.

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


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

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

## Is CVE-2025-13307 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-13307 is a high-severity code injection vulnerability in Unknown Ocean Modal Window, published on 19 Dec 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-13307 exists.

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

## Sources

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

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