Cyber Resilience

CVE-2026-25863

Public PoC
Published
04 May 2026
Modified
17 June 2026
CVSS Score v4 8.7
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.0045 38th percentile
Risk Priority 44 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2026-25863 is a high-severity Improper Validation of Specified Quantity in Input (CWE-1284) vulnerability in Wordpress (inferred from references). Its CVSS base score is 8.7 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 38th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2026-25863 is an uncontrolled resource consumption vulnerability (CWE-1284) in the Conditional Fields for Contact Form 7 WordPress plugin through version 2.6.7. The flaw exists in the Wpcf7cfMailParser class's hide_hidden_mail_fields_regex_callback() method, which reads an iteration count directly from user-supplied POST parameters without validation or upper bound enforcement, enabling unbounded loop execution with multiple preg_replace() operations.

Unauthenticated attackers can exploit the vulnerability remotely via the REST API endpoint by supplying an arbitrarily large integer value in POST parameters. This causes excessive resource consumption, exhausting server memory and crashing the PHP process, resulting in denial of service. The issue carries a CVSS v3.1 base score of 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H), highlighting high availability impact with no requirements for privileges or user interaction.

Mitigation guidance is available in advisories such as the VulnCheck report at https://www.vulncheck.com/advisories/conditional-fields-for-contact-form-7-dos-via-uncontrolled-resource-consumption and the plugin's developer documentation at https://wordpress.org/plugins/cf7-conditional-fields/#developers.

EU & UK References

Vulnerability Data

Conditional Fields for Contact Form 7 WordPress plugin through version 2.7.2 contains an uncontrolled resource consumption vulnerability in the Wpcf7cfMailParser class where the hide_hidden_mail_fields_regex_callback() method reads an iteration count directly from user-supplied POST parameters without validation or upper bound enforcement.…

more

Unauthenticated attackers can supply an arbitrarily large integer value through the REST API endpoint to cause unbounded loop execution with multiple preg_replace() operations, exhausting server memory and crashing the PHP process.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
T1212 Exploitation for Credential Access Credential Access
Adversaries may exploit software vulnerabilities in an attempt to collect credentials.
T1499 Endpoint Denial of Service Impact
Adversaries may perform Endpoint Denial of Service (DoS) attacks to degrade or block the availability of services to users.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-43793Shared CWE-1284
CVE-2021-43267Shared CWE-1284
CVE-2024-21953Shared CWE-1284
CVE-2026-27171Shared CWE-1284
CVE-2025-10094Shared CWE-1284
CVE-2023-31310Shared CWE-1284
CVE-2025-36428Shared CWE-1284
CVE-2025-46656Shared CWE-1284
CVE-2026-30573Shared CWE-1284
CVE-2023-30082Shared CWE-1284

Affected Assets

Wordpress
—
inferred from references and description; NVD did not file a CPE for this CVE

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V6.7.2
  • V1.4.2
  • V2.1.1
  • V2.2.1

Mitigating Controls (NIST 800-53 r5) AI

SI-10 requires validity checks on information inputs, directly stopping acceptance of malformed quantities before they can be used.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 partial match
prevents

Secure SDLC practices directly require proper quantity/length validation in input handling.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

prevents

Secure development lifecycle mandates input validation for quantity fields, directly preventing CWE-1284.

prevents

Application security requirements explicitly call for validation of size/length inputs, mitigating CWE-1284.

prevents

Secure architecture principles encourage robust input handling but do not specifically address quantity validation.

prevents

Secure coding standards require explicit checks on numeric quantity inputs, fully addressing CWE-1284.

finds

Security testing in development can detect missing quantity validation but does not itself implement the control.

References