Skip to main content

WP Rocket EUVDEUVD-2026-95510

| CVE-2026-97076 HIGH
Executable Regular Expression Error (CWE-624)
2026-10-09 Patchstack GHSA-cvhh-7x6j-w7v5
7.5
CVSS 3.1 · Vendor: Patchstack
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Send crafted HTTP request to WP Rocket
  2. Exploit
    Trigger vulnerable regular expression processing
  3. Impact
    Exhaust server CPU/resources (denial of service)

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V2 - Validation and Business Logic Executable regular expression
Exploitation Conditions

Exploitable against default configurations of WP Rocket versions prior to 3.23.5 with no authentication, no user interaction, and low attack complexity (AV:N/AC:L/PR:N/UI:N) - the attacker only needs network reachability to the WordPress site. The limiting factor is impact scope: per the CVSS vector the consequence is availability loss only (C:N/I:N), i.e. a denial-of-service condition rather than data exposure or takeover. Note the description/CWE label this 'Code Injection,' which if accurate would broaden the required conditions and impact; this is unverified and conflicts with the scored vector.

Impact

Signals conflict and must be reconciled before prioritization. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, base 7.5) describes a remote, low-complexity, unauthenticated flaw with impact restricted to AVAILABILITY only (C:N/I:N) - i.e. a denial-of-service condition. This is corroborated by the single Patchstack reference, whose URL slug explicitly reads 'denial-of-service-attack-vulnerability.' However, the CVE Description and CWE-624 (Executable Regular Expression Error) both characterize the issue as 'Code Injection,' which would normally imply confidentiality/integrity impact - directly contradicting the C:N/I:N in the vector. This discrepancy should be resolved with the vendor/Patchstack: the quantitative data (CVSS A:H-only + reference title) strongly favors a ReDoS/availability bug rather than true code execution. No EPSS score, no CISA KEV listing, and no public POC are present in the provided data, so there is no evidence of active or at-scale exploitation. Net: this is a plausibly real but availability-only issue in a very widely deployed plugin; treat as a patch-soon item (especially for internet-facing WordPress sites) rather than an emergency, pending clarification of whether 'Code Injection' is accurate or a mislabel of a DoS.

Exploit ScenarioDerived

An unauthenticated remote attacker sends specially crafted input to an affected WP Rocket endpoint that is processed by a vulnerable regular expression, triggering catastrophic backtracking (or injected regex evaluation) that consumes CPU/memory and renders the WordPress site unresponsive. Because AV:N/AC:L/PR:N/UI:N, no authentication, user interaction, or special timing is required against a default install. No public exploit code was identified at time of analysis.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.3% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 09, 2026

Denial-of-service condition in WP Rocket versions before 3.23.5 can be triggered by unauthenticated remote attackers with no user interaction, according to the assessed CVSS vector; however, the advisory and CWE-624 label also carry a 'Code Injection' claim that conflicts with the availability-only impact and remains unverified. The affected product is the WP Rocket WordPress plugin from WP Media, and the supplied intelligence does not indicate CISA KEV active exploitation; no public exploit code identified at time of analysis. Because the vector scores C:N/I:N/A:H, treat the confirmed impact as resource-exhaustion/DoS rather than data compromise or site takeover unless code-injection evidence emerges.

RemediationAI

Vendor-released patch: WP Rocket 3.23.5. Upgrade the WP Rocket plugin to 3.23.5 or later, preferably through the WordPress plugin update mechanism or by downloading the fixed release from the vendor, and verify the installed version after updating. If immediate patching is not possible, a compensating control is to temporarily deactivate the WP Rocket plugin, accepting the loss of caching/optimization and possible performance degradation; alternatively, deploy a WAF or virtual patching rule from Patchstack/the vendor if available, but note that the conflicting code-injection wording means DoS-focused virtual patching may not cover all theoretical attack paths. Consult the Patchstack advisory for affected-version details and any updated guidance: https://patchstack.com/database/wordpress/plugin/wp-rocket/vulnerability/wordpress-wp-rocket-plugin-3-23-5-denial-of-service-attack-vulnerability?_s_id=cve.

Affected VersionsENISA

WP Rocket 0 <3.23.5

Affected Packages

euvd wp_rocket fix: 3.23.5

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

CWE-624 (Executable Regular Expression Error) points to unsafe handling of attacker-influenced regular expressions in the WP Rocket WordPress plugin, where malformed or specially crafted regex input can cause unintended behavior in the regex processing path. The CPE cpe:2.3:a:wp_media:wp_rocket:*:*:*:*:*:*:*:* identifies the affected component as WP Media's WP Rocket plugin for WordPress, with all versions before 3.23.5 in range. The provided Patchstack reference is titled a denial-of-service attack vulnerability, and the authoritative assessed vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H) indicates the practical consequence is availability loss; the 'Code Injection' wording in the description would imply a broader integrity/confidentiality impact but is not corroborated by the scored metrics, so it should be treated as an unresolved discrepancy rather than a confirmed code-execution condition.

Know when Wp Rocket gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (Patchstack) PRIMARY 7.5 HIGH
AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
vuln.today AI 7.5 HIGH

Remote unauthenticated input to a vulnerable regex (AV:N/AC:L/PR:N/UI:N); impact is availability-only (A:H, C:N/I:N) consistent with the DoS reference despite the 'Code Injection' label.

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (Patchstack).

CVSS VectorVendor: Patchstack

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

Lifecycle Timeline

2
Patch available
Oct 09, 2026 - 08:16 EUVD
CVE Published
Oct 09, 2026 - 07:00 cve.org
HIGH 7.5

DescriptionCVE.org

Executable Regular Expression Error vulnerability in WP Media WP Rocket wp-rocket allows Code Injection.This issue affects WP Rocket: from n/a before 3.23.5.

Executive ViewAI

Why It Matters

WP Rocket, a popular WordPress caching plugin, contains a high-severity denial-of-service vulnerability (CVE-2026-97076) affecting versions before 3.23.5. If exploited, this flaw could render WordPress sites unavailable to customers and employees, disrupting online operations and potentially damaging revenue and brand trust. No public exploit has been identified at time of analysis, but the absence of a vendor patch and the availability-only impact warrant management attention to ensure interim mitigations are in place.

Business Impact: High
Compensating Controls

Interim mitigations include deploying WAF rules to block exploit attempts, disabling the WP Rocket plugin if not essential, implementing rate limiting, and monitoring for denial-of-service indicators. No vendor-released patch identified at time of analysis.

Threat Intelligence Overview

EPSS Score
0.3%
Top 80% exploitable
Prevalence
High
WP Rocket is one of the most popular premium WordPress caching plugins
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.3%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
Yes
Human Impact
High
Technical Impact
Partial

Priority Score

38
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +38
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Code Injection CRITICAL

Code injection occurs when an application accepts user input and passes it directly into a language interpreter or evaluator without proper sanitization.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy