CVE-2025-47947 | ModSecurity Has Possible DoS Vulnerability

Exp

ModSecurity is an open source, cross platform web application firewall (WAF) engine for Apache, IIS and Nginx. Versions up to and including 2.9.8 are vulnerable to denial of service in one special case (in stable released versions): when the payload's content type is `application/json`, and there is at least one rule which does a `sanitiseMatchedBytes` action. A patch is available at pull request 3389 and expected to be part of version 2.9.9. No known workarounds are available.

Published: 2025-05-21 Last update: 2025-06-20 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2025-47947 is rated High Exploit Risk (69.6/100): CVSS High severity, with medium exploitation likelihood (EPSS 0.61%). 1 public exploit reference(s) are indexed (Exploit-DB). Public exploits are available—assess exposure, apply mitigations, and prioritize patching.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Public exploit references (Exploit-DB) for CVE-2025-47947

EDB-ID Source Kind Published Link
— nvd_ref exploit_tag Exploit-DB ↗

Exploit prediction scoring system (EPSS) score for CVE-2025-47947

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-04-19 0.51% 0.61% +0.10%
2 2026-03-17 0.17% 0.51% +0.34%
3 2025-11-24 — 0.17% —

Full EPSS history (9 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2025-47947

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.5 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 3.9 3.6 [email protected]

Weakness enumeration for CVE-2025-47947

OS Trackers for CVE-2025-47947

vendor priority summary link
debian not yet assigned CVE-2025-47947 not yet assigned priority: Debian including 1 source packages (modsecurity-apache), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2025-47947
redhat high — https://access.redhat.com/security/cve/CVE-2025-47947
suse high CVE-2025-47947 severity important: SUSE including 9 source package names (apache2-mod_security2-2.8.0-7.9.1, apache2-mod_security2-2.9.10-1.1, …), 29 product×package rows across 27 product lines (SUSE Enterprise Storage 7.1, SUSE Liberty Linux 8, … (27 product lines)): Fixed 29. https://www.suse.com/security/cve/CVE-2025-47947/
ubuntu medium CVE-2025-47947 medium priority: Ubuntu including 2 source packages (modsecurity, modsecurity-apache), 17 status rows across 10 suites (bionic, focal, jammy, noble, oracular, plucky, questing, trusty, upstream, xenial): released 9, not-affected 7, needs-triage 1. https://ubuntu.com/security/CVE-2025-47947

Affected software / configurations for CVE-2025-47947

Vendor Product Version Raw CPE
trustwave modsecurity < 2.9.9 cpe:2.3:a:trustwave:modsecurity:*:*:*:*:*:*:*:*

References for CVE-2025-47947

cvelogic Threat Intelligence