ZeusCart 4.0 contains a cross-site request forgery vulnerability that allows attackers to perform unauthorized actions on behalf of victims by crafting malicious requests. Attackers can deactivate customer accounts via the admin interface by tricking users into visiting attacker-controlled pages that submit requests to the regstatus endpoint with action=deny parameters.
Security readout for executives and security teams
Plain-English summary
ZeusCart 4.0 has a CSRF flaw that can let an attacker misuse a logged-in administrator's browser to deactivate customer accounts. The business impact is account disruption and support burden, not direct data theft based on the supplied sources.
Executive priority
Treat this as a moderate operational risk. Prioritize it if ZeusCart 4.0 is internet-facing, still used for customer management, or has privileged admins who browse externally during active sessions.
Technical view
The issue is CWE-352 in ZeusCart 4.0. A crafted cross-site request can trigger unauthorized customer account status changes through the admin interface when an administrator is induced to interact with attacker-controlled content. The supplied CVSS v4.0 score is 6.9.
Likely exposure
Exposure is limited to organizations running ZeusCart 4.0, especially where administrators access the application from browsers that can reach untrusted pages.
Exploitation context
The CVE bundle cites an ExploitDB entry, so public exploit information exists. KEV is false, and the supplied sources do not show confirmed active exploitation.
Researcher notes
Evidence supports CSRF-driven account deactivation in ZeusCart 4.0. The source bundle does not provide a vendor patch, fixed version, or active exploitation confirmation. Avoid assuming broader account takeover or data compromise without additional evidence.
Mitigation direction
Check ZeusCart vendor or maintainer guidance for an official fix or supported upgrade path.
Restrict access to the ZeusCart admin interface to trusted networks or VPN users.
Review administrator browsing practices and separate admin sessions from general web browsing.
Apply CSRF protections if maintaining a private fork or custom deployment.
Monitor for unexpected customer account deactivations.
Validation and detection
Confirm whether any production or legacy systems run ZeusCart 4.0.
Review admin routes for CSRF token enforcement on account status changes.
Check logs for unusual bursts of customer account deactivation activity.
Verify admin interface exposure from the internet or untrusted networks.
Document compensating controls if no vendor patch is available.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-352: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-352 · source CWE mapping
Cross-Site Request Forgery (CSRF)
Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.