Cyber Resilience

CVE-2023-46393

Gougucms 4.08.18

Public PoC
Published
27 October 2023
Modified
21 November 2024
CVSS Score v3.1 7.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
EPSS Score 0.0045 37th percentile
Risk Priority 57 floored blend · peak EPSS

Summary

CVE-2023-46393 is a high-severity Improper Cleanup on Thrown Exception (CWE-460) vulnerability in Gougucms Gougucms. Its CVSS base score is 7.5 (High).

Operationally, ranked at the 37th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

gougucms v4.08.18 was discovered to contain a password reset poisoning vulnerability which allows attackers to arbitrarily reset users' passwords via a crafted packet.

CWE(s)

Related Threats

CVEs Like This One

CVE-2023-46394Same product: Gougucms Gougucms
CVE-2023-3035Same vendor: Gougucms
CVE-2025-59399Shared CWE-460
CVE-2024-20354Shared CWE-460
CVE-2024-0316Shared CWE-460
CVE-2025-69652Shared CWE-460
CVE-2025-30157Shared CWE-460
CVE-2026-33481Shared CWE-460
CVE-2026-20118Shared CWE-460
CVE-2025-32439Shared CWE-460

Affected Assets

gougucms
gougucms
4.08.18

Mitigating Controls

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 mostly match
prevents

Secure SDLC practices directly enforce proper exception handling and resource cleanup.

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.

finds

Security testing can detect missing cleanup paths, thereby mitigating the weakness before deployment.

prevents

Secure SDLC mandates exception-handling and cleanup practices that reduce improper state after thrown exceptions.

prevents

Application security requirements can specify robust exception handling and resource-release rules.

prevents

Secure architecture principles include designing for safe failure and guaranteed cleanup on exceptions.

prevents

Secure coding standards directly require proper resource release and state restoration after exceptions.

References