CVE-2023-39343
Sulu 2.5.0 – 2.5.10
Raw vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:NCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS, Forum of Incident Response and Security Teams (FIRST), epss.first.org. Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2023-39343 is a medium-severity Observable Response Discrepancy (CWE-204) vulnerability in Sulu. Its CVSS base score is 4.3 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Network Security Appliances (T1590.006); ranked in the top 49% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-2374
Vulnerability Data
Sulu is an open-source PHP content management system based on the Symfony framework. It allows over the Admin Login form to detect which user (username, email) exists and which one do not exist. Sulu Installation not using the old Symfony…
more
5.4 security System and previous version are not impacted by this Security issue. The vulnerability has been patched in version 2.5.10.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
MITRE ATT&CK v20.0
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V13.4.5
Likely Mitigating Controls
Our mappings. Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Mitigating Controls (NIST CSF 2.0)
Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→CSF cross-walk — links open the control.
Secure SDLC practices directly prevent introduction of inconsistent response behavior that leaks internal state.
Mitigating Controls (ISO/IEC 27001:2022 Annex A)
Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→ISO cross-walk — links open the control.
Security testing can detect observable response discrepancies before deployment.
Training developers about information disclosure through error messages reduces instances of CWE-204, since the weakness is often a knowledge gap (developer doesn't realize differing responses leak validity), but it is a specific implementation detail requiring careful coding practice that training alone does not guarantee, similar to the A.6.3 -> CWE-598 anchor.
Secure coding standards explicitly require uniform error handling to prevent information leakage.
A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so it reduces ordinary software CWEs in delivered code the way those practices do; CWE-204 is a regular code-level weakness (different responses revealing internal state) that secure coding and testing practices partially prevent, and A.8.30 sits at its declared ceiling of `partial` on this verb.
Strong authentication reduces information leakage from authentication responses.