CVE-2025-12886
WordPress vulnerability analysis and mitigation

Overview

CVE-2025-12886 is an unauthenticated Server-Side Request Forgery (SSRF) vulnerability in the Oxygen – WooCommerce WordPress Theme by Laborator, affecting all versions up to and including 6.0.8. The flaw exists in the laborator_calc_route AJAX action, which allows unauthenticated attackers to make arbitrary web requests originating from the server. It was published on March 28, 2026, and assigned by Wordfence. The vulnerability carries a CVSS v3.1 base score of 7.2 (High) (Wordfence, Red Hat CVE).

Technical details

The root cause is classified as CWE-918 (Server-Side Request Forgery), where the laborator_calc_route AJAX action fails to validate or restrict user-supplied URL/route parameters before issuing server-side HTTP requests. Because the endpoint is accessible without authentication, any remote attacker can supply an arbitrary destination URL. The changed scope (S:C) in the CVSS vector reflects that the impact extends beyond the vulnerable component itself, potentially reaching internal services not directly exposed to the internet. No authentication or user interaction is required, and attack complexity is low (Wordfence, Infinitsec).

Impact

Successful exploitation allows an unauthenticated attacker to use the vulnerable WordPress server as a proxy to query internal network services, cloud metadata endpoints (e.g., AWS IMDSv1), or other resources not directly accessible from the internet. This can result in limited confidentiality and integrity impacts — including exposure of internal service responses and potential modification of data via internal APIs — though availability is not directly affected. In cloud-hosted environments, SSRF can be leveraged to retrieve instance metadata credentials, enabling further lateral movement or privilege escalation (Wordfence).

Exploitability

No public exploit code or active in-the-wild exploitation has been reported as of the time of publication. The EPSS score is approximately 0.039%, indicating a low probability of exploitation in the near term. The vulnerability is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog. However, the unauthenticated nature and low attack complexity make it straightforward to exploit if a vulnerable theme version is publicly accessible (Wordfence, Red Hat CVE).

Exploitation steps

  1. Reconnaissance: Identify WordPress sites running the Oxygen – WooCommerce WordPress Theme (by Laborator) version ≤ 6.0.8 using tools like WPScan, Shodan, or by inspecting theme metadata in page source (/wp-content/themes/oxygen/style.css).
  2. Locate the vulnerable AJAX endpoint: The vulnerable action is registered as a WordPress AJAX handler accessible at wp-admin/admin-ajax.php with the action parameter laborator_calc_route.
  3. Craft the SSRF request: Send an unauthenticated HTTP POST request to https://target.com/wp-admin/admin-ajax.php with the body action=laborator_calc_route&routepath=http://169.254.169.254/latest/meta-data/ (or any internal/arbitrary URL).
  4. Retrieve internal service response: The server fetches the specified URL and may return the response to the attacker, exposing internal network resources, cloud metadata, or other sensitive service data.
  5. Escalate if applicable: In cloud environments, use retrieved metadata credentials (e.g., IAM role tokens from AWS IMDSv1) for further lateral movement or privilege escalation (Infinitsec, Wordfence).

Indicators of compromise

  • Network: Outbound HTTP requests from the WordPress server to internal IP ranges (e.g., 10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16) or cloud metadata endpoints (169.254.169.254).
  • Logs: WordPress access logs showing POST requests to /wp-admin/admin-ajax.php with action=laborator_calc_route and unusual or internal routepath parameter values; web server error logs indicating failed connections to internal hosts.
  • Process/Application: Unexpected outbound HTTP connections initiated by the PHP/web server process to non-standard destinations, particularly metadata services or internal APIs.

Mitigation and workarounds

Users should update the Oxygen – WooCommerce WordPress Theme to version 6.0.9 or later, which addresses this vulnerability per the Laborator release notes. As a temporary workaround, site administrators can restrict access to wp-admin/admin-ajax.php for unauthenticated users via WAF rules or server-level access controls, or disable the theme if it is not actively in use. Implementing egress filtering on the web server to block outbound requests to internal IP ranges and cloud metadata endpoints will reduce the risk of SSRF exploitation (Laborator Release Notes, Wordfence).

Community reactions

Wordfence published the vulnerability in their weekly WordPress vulnerability report for the week of March 23–29, 2026, noting the unauthenticated SSRF risk. RedPacket Security and Mastodon security community accounts shared alerts about the CVE shortly after disclosure. No major vendor statements beyond the Laborator release notes or significant media coverage have been identified (Wordfence Weekly Report, RedPacket Security).

Additional resources


SourceThis report was generated using AI

Related WordPress vulnerabilities:

CVE ID

Severity

Score

Technologies

Component name

CISA KEV exploit

Has fix

Published date

CVE-2026-77115HIGH7.1
  • brave-popup-builder
NoYesAug 23, 2026
CVE-2026-77116MEDIUM4.3
  • brave-popup-builder
NoYesAug 23, 2026
CVE-2026-14853MEDIUM4.3
  • woocommerce-bookings
NoYesAug 23, 2026
CVE-2026-77003LOW2.7
  • content-mask
NoYesAug 23, 2026
CVE-2026-13598NONEN/A
  • restrictmate
NoYesAug 23, 2026

Free Vulnerability Assessment

Benchmark your Cloud Security Posture

Evaluate your cloud security practices across 9 security domains to benchmark your risk level and identify gaps in your defenses.

Request assessment

Get a personalized demo

Ready to see Wiz in action?

"Best User Experience I have ever seen, provides full visibility to cloud workloads."
David EstlickCISO
"Wiz provides a single pane of glass to see what is going on in our cloud environments."
Adam FletcherChief Security Officer
"We know that if Wiz identifies something as critical, it actually is."
Greg PoniatowskiHead of Threat and Vulnerability Management