# CVE-2025-69299: WordPress Oxygen theme <= 6.0.8 - Server Side Request Forgery (SSRF) vulnerability

> An attacker can exploit a Server-Side Request Forgery vulnerability in the Oxygen WordPress theme to make arbitrary requests from the server.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/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:** 20 Feb 2026
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-p95v-rww3-j83p

## What is CVE-2025-69299?

CVE-2025-69299 is a high-severity server-side request forgery vulnerability in Laborator Oxygen, published on 20 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Server-Side Request Forgery (SSRF) vulnerability in Laborator Oxygen oxygen allows Server Side Request Forgery.This issue affects Oxygen: from n/a through <= 6.0.8.

Weakness: CWE-918 (Server-Side Request Forgery)

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


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

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

## Is CVE-2025-69299 being exploited?

There is no known exploitation of CVE-2025-69299 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2025-69299 is a high-severity server-side request forgery vulnerability in Laborator Oxygen, published on 20 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-69299 in the wild and no public exploit code.

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

## Sources

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

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