CVE-2024-11094
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:NCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2024-11094 is a medium-severity Exposure of Data Element to Wrong Session (CWE-488) vulnerability in Wordpress (inferred from references). Its CVSS base score is 5.3 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique NTDS (T1003.003); ranked at the 31th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and AC-4 (Information Flow Enforcement) — see the control section below for these in your framework.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-33647
Vulnerability Data
The 404 Solution plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 2.35.17 via the export feature. This makes it possible for unauthenticated attackers to extract data such as redirects including GET parameters…
more
which may reveal sensitive information. On most sites this is unlikely to be the case.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
AC-3 enforces access decisions that can be scoped to the correct session context.
AC-4 controls information flows between entities, reducing cross-session leakage.
SC-4 directly stops unintended transfer of data through shared resources that different sessions may access.
SC-39 isolates execution domains so one session cannot reach another's state or data.
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.
Enforcing authorization policies and least privilege can prevent cross-session data exposure when session separation is treated as an access rule.
Protecting data-in-use directly addresses runtime leakage of session data to unauthorized contexts.
Logical access controls and segmentation can be applied to isolate session state within applications or environments.
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.
Secure development lifecycle practices include session-management controls that prevent exposure of data to the wrong session.
Application security requirements explicitly call for proper session isolation and state management.
A.8.27 mandates security-by-design principles (defense-in-depth, least privilege, default-deny, fail-securely, distrust-external-input, zero-trust never-trust/always-verify, session control, data validation/sanitization, and explicit boundary enforcement across architecture layers) that directly stop session data from crossing to the wrong session; the bounded remainder is implementation defects that slip past even a well-applied review against known attack patterns.
Secure coding standards mandate correct session handling to prevent exposure of data elements to the wrong session.
Security testing can detect the weakness but does not itself implement the preventive control.