Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessSend crafted request with attacker-controlled address
-
ExploitValue stored unvalidated as option key
-
ExecutionRepeat to grow option without bound
-
ImpactSite 404/missing-page handling degrades
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V2 - Validation and Business Logic Resource consumption limits
MITRE ATT&CK
1 technique across 1 tactic: Impact The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | No special conditions - remote unauthenticated exploitation against default configurations of the Really Simple Security WordPress plugin (versions 8.1.6 up to but not including 9.8.3). The attacker only needs network reachability to the site; the vulnerable option-key storage is part of the plugin's normal request handling, so no authentication, user interaction, or non-default setting is required. The practical limit on impact is that the outcome is gradual availability degradation (slower missing-page/404 handling and unbounded option growth) rather than a complete outage or any data compromise, and sites not running this plugin (or already on 9.8.3+) are unaffected. |
| Impact | This is a low-to-moderate real-world risk that is correctly rated: the vendor CVSS of 5.3 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L) reflects an availability-only impact with no confidentiality or integrity effect, and I agree with it. CWE-400 (uncontrolled resource consumption) matches the description: an unauthenticated attacker supplies an unvalidated client address that is used as a storage key in one of the plugin's own options, allowing that option row to grow without bound and slowing the site's handling of missing (404) pages. The A:L (not A:H) is appropriate - the described effect is degraded performance of missing-page handling and option bloat, not a full site outage. A public POC exists (WPScan) and a patch is available in 9.8.3, but there is no EPSS score, no CISA KEV listing, and no evidence of active exploitation in the provided data - so this is 'exploit code exists' rather than 'exploited.' Because the payoff is only gradual performance degradation / database bloat rather than data theft or code execution, this is a patch-in-normal-cycle item, not an emergency, despite the large install base of the plugin. No signals conflict; the main missing signals are EPSS and any exploitation telemetry. |
| Exploit ScenarioDerived | An unauthenticated attacker sends a stream of HTTP requests to the target WordPress site, each carrying a distinct crafted client-supplied address value that Really Simple Security stores verbatim as a key inside one of its own options. Repeated requests grow that option row without bound, bloating the database and progressively slowing the site's handling of missing/404 pages. A public proof-of-concept is available via WPScan, and no authentication or user interaction is required. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 18, 2026
Unauthenticated remote attackers can inflate a plugin option in the Really Simple Security WordPress plugin (versions 8.1.6 up to but not including 9.8.3) by supplying arbitrary address values that the plugin uses as storage keys without validation, causing unbounded option growth and slower handling of missing pages. The impact is availability-only degradation (CVSS 5.3, AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L) with no confidentiality or integrity effect, and default configurations are reachable by network unauthenticated exploitation as long as the site is online. Publicly available exploit code exists and WPScan published the finding, but there is no indication of confirmed active exploitation (CISA KEV); sites running 9.8.3 or later are unaffected.
RemediationAI
Vendor-released patch: update Really Simple Security to 9.8.3 or later, which is the only complete fix and is available from the vendor per the WPScan advisory at https://wpscan.com/vulnerability/e658dcd2-2ff6-4611-a28d-e2482c65be8b/ and the NVD entry at https://nvd.nist.gov/vuln/detail/CVE-2026-88798. If immediate patching is not possible, apply rate limiting or a WAF rule that rejects abnormally frequent requests carrying unusual client-supplied address values before they reach the plugin, accepting that this may affect legitimate traffic and produce false positives that require threshold tuning. You can also monitor and periodically prune the affected plugin option to bound growth, but that is reactive cleanup and will not prevent an attacker from re-inflating it. Because the issue is unauthenticated and affects normal request handling, blocking anonymous access or disabling plugin endpoints would be an over-broad measure that breaks expected site functionality and should be reserved as a last resort.
Affected VersionsENISA
Affected Packages
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
This is an uncontrolled resource consumption issue (CWE-400) in a WordPress plugin. Really Simple Security takes a client-supplied address value from incoming requests and uses it directly as a storage key inside one of its own stored options, without validating, normalizing, or bounding it. Because the key space is fully attacker-controlled, repeated requests with distinct address values cause that option to accumulate entries indefinitely; as the stored payload grows, reads and writes of the option become progressively more expensive, which surfaces as slower handling of missing pages (404 requests) that consult the same option. The CPE entry cpe:2.3:a:unknown:really_simple_security:*:*:*:*:*:*:*:* records the affected component but does not resolve a definitive vendor namespace, so the authoritative scope comes from the plugin advisory, reported by WPScan and tracked as ENISA EUVD-2026-82676.
Know when Really Simple Security 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
AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
Unauthenticated remote request with no interaction (AV:N/AC:L/PR:N/UI:N); unbounded option growth degrades but does not fully deny service, so A:L with C:N/I:N.
Primary rating from Vendor (WPScan).
CVSS VectorVendor: WPScan
Lifecycle Timeline
3DescriptionCVE.org
The Really Simple Security WordPress plugin before 9.8.3 does not validate a client-supplied address value before using it as a storage key in one of its own options, allowing unauthenticated attackers to grow that option without bound and to slow the site's handling of missing pages.
Threat Intelligence Overview
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.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Denial of Service attacks render applications or systems unavailable by overwhelming resources or triggering failure conditions.
More in Really Simple Security
View allThe Really Simple Security (Free, Pro, and Pro Multisite) plugins for WordPress are vulnerable to authentication bypass
Two-factor authentication bypass in the Really Simple Security WordPress plugin (versions before 9.8.1) allows an attack
Two-factor authentication bypass in the Really Simple Security WordPress plugin before 9.5.10.1 allows attackers who alr
Improper privilege management in the Really Simple Security WordPress plugin before 9.8.0 permits a subsite administrato
EUVD-2026-82676
GHSA-43h4-q789-j3pr
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB