Security 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

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

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, exploitation aligns with the MITRE ATT&CK technique Junk Data (T1001.001); 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)

A10:2025 Mishandling of Exceptional Conditions

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)
NVD-CWE-noinfoCWE-460

Related Threats

MITRE ATT&CK Enterprise Techniques

T1001.001 Junk Data Command And Control
Adversaries may add junk data to protocols used for command and control to make detection more difficult.
attack.mitre.org →
T1001.003 Protocol or Service Impersonation Command And Control
Adversaries may impersonate legitimate protocols or web service traffic to disguise command and control activity and thwart analysis efforts.
attack.mitre.org →
T1003.007 Proc Filesystem Credential Access
Adversaries may gather credentials from the proc filesystem or `/proc`.
attack.mitre.org →
T1007 System Service Discovery Discovery
Adversaries may try to gather information about registered local system services.
attack.mitre.org →
T1008 Fallback Channels Command And Control
Adversaries may use fallback or alternate communication channels if the primary channel is compromised or inaccessible in order to maintain reliable command and control and to avoid data transfer thresholds.
attack.mitre.org →
T1010 Application Window Discovery Discovery
Adversaries may attempt to get a listing of open application windows.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-46394Same product: Gougucms Gougucms
CVE-2025-32439Shared CWE-460
CVE-2025-30157Shared CWE-460
CVE-2026-20118Shared CWE-460
CVE-2024-20354Shared CWE-460
CVE-2025-69652Shared CWE-460
CVE-2026-93710Shared CWE-460
CVE-2024-0316Shared CWE-460
CVE-2026-33481Shared CWE-460
CVE-2025-59399Shared 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 partial match
blocks

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.

A.7.4 Physical security monitoring partial match
removes
A.8.16 Monitoring activities partial match
removes
A.8.19 Installation of software on operational systems partial match
removes
A.8.25 Secure development life cycle partial match
blocks

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

A.8.26 Application security requirements partial match
blocks

A.8.26 requires identifying and specifying security requirements (including resilience against attacks like SQL injection) during development or acquisition; it does not itself implement exception handling or cleanup logic that would stop CWE-460 from being exploitable.

A.8.27 Secure system architecture and engineering principles partial match
blocks

A.8.27 mandates establishing and applying secure engineering principles (including secure-by-design, least privilege, fail-securely, and design reviews) but does not itself stop an exception-cleanup defect from being introduced in code or from being exploitable once present; the weakness can still be exploited.

References