dbcve.org
Server-Side Request Forgery (SSRF)Weakness · CWE-918

CVE-2025-12886

HIGH · 7.2 CVSS v3.1 Published 2026-03-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The Oxygen Theme theme for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 6.0.8 via the laborator_calc_route AJAX action. This makes it possible for unauthenticated attackers to make web requests to arbitrary locations originating from the web application and can be used to query and modify information from internal services.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Oxygen Theme for WordPress contains an unauthenticated Server-Side Request Forgery (SSRF) vulnerability in the laborator_calc_route AJAX action through version 6.0.8. Attackers can abuse this to make arbitrary HTTP requests from the server, potentially reaching internal services and exfiltrating data or pivoting to internal network resources.

MitigationUpdate Oxygen Theme to a version beyond 6.0.8 immediately. If no patch is available, consider removing the theme or implementing input validation/allowlist controls on the affected AJAX endpoint.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Oxygen Theme is installed
    Check the WordPress themes directory (wp-content/themes/) for the oxygen theme folder, or query the WordPress database: SELECT theme FROM wp_themes WHERE name = 'Oxygen' or check wp_options for active_theme.
    Affected if Oxygen Theme folder exists in wp-content/themes/ or theme is registered in WordPress
  2. Identify installed Oxygen Theme version
    Open the style.css file in the oxygen theme folder and read the 'Version:' header, or query the WordPress database: SELECT option_value FROM wp_options WHERE option_name = 'oxygen_theme_version' or check theme file headers.
    Affected if Version is 6.0.8 or earlier (any version through 6.0.8 is affected)
  3. Check if laborator_calc_route AJAX action is exposed
    Test by making a POST request to /wp-admin/admin-ajax.php with action=laborator_calc_route parameter. No authentication should be required for this vulnerability. Use: curl -X POST https://your-site.com/wp-admin/admin-ajax.php -d 'action=laborator_calc_route'
    Affected if The AJAX endpoint responds without requiring authentication (returns 200 OK rather than 403 or requiring login)
  4. Verify WordPress site is publicly accessible
    Confirm the target WordPress site is reachable over the internet. The SSRF is exploitable by unauthenticated remote attackers, so an internet-facing site is required for exploitation.
    Affected if The WordPress site is exposed to the internet (not behind VPN or restricted network)

If Oxygen Theme version 6.0.8 or earlier is installed AND the site is internet-facing AND the laborator_calc_route AJAX action is accessible without authentication, the environment is affected by this SSRF vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Oxygen Theme to a version beyond 6.0.8 immediately. If no patch is available, consider removing the theme or implementing input validation/allowlist controls on the affected AJAX endpoint.

Recommended fix High confidence

Oxygen Theme version 6.0.9 or latest stable release

  1. Log in to the WordPress admin dashboard
  2. Navigate to Appearance > Themes
  3. Deactivate the current Oxygen Theme
  4. If you have a child theme, ensure it is also updated or temporarily switch to a default theme
  5. Delete the vulnerable Oxygen Theme
  6. Install the latest version of the Oxygen Theme (version 6.0.9 or later)
  7. Activate the new version
  8. Verify the laborator_calc_route AJAX action is no longer accessible to unauthenticated users or confirm the vulnerability is patched

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-12886 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-12886 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data