CVE-2025-70141: SourceCodester Customer Support System 1.0 contains an incorrect access control vulnerability in ajax.php.
SourceCodester Customer Support System 1.0 contains an incorrect access control vulnerability in ajax.php. The AJAX dispatcher does not enforce authentication or authorization before invoking administrative methods in admin_class.php based on the action parameter. An unauthenticated remote attacker can perform sensitive operations such as creating customers and deleting users (including the admin account), as well as modifying or deleting other application records (tickets, departments, comments), resulting in unauthorized data modification.
Security readout for executives and security teams
Plain-English summary
Customer Support System 1.0 may allow anyone who can reach its web interface to perform administrative changes without signing in. Attackers could create customer accounts, delete users—including administrators—and alter or remove tickets, departments, comments, and other records. This creates substantial integrity and availability risk, with some potential disclosure risk.
Executive priority
Treat reachable deployments as an immediate remediation priority because compromise requires no account or user interaction and can disrupt support operations or corrupt records. Isolate exposure promptly, validate data integrity, and obtain vendor remediation guidance. Escalate incident review if logs or records show unexplained administrative changes.
Technical view
The ajax.php dispatcher invokes administrative methods in admin_class.php according to an action parameter without first enforcing authentication or authorization. The issue is remotely reachable, requires no privileges or user interaction, and is classified as missing authentication and authorization controls (CWE-306 and CWE-862). CVSS 3.1 scores it 9.4 critical.
Likely exposure
Exposure is likely where SourceCodester Customer Support System 1.0 is deployed and ajax.php is reachable by untrusted users. Internet-facing installations are the highest concern. The supplied affected-product metadata is incomplete, so organizations should confirm product identity and version directly rather than relying only on automated CPE inventory.
Exploitation context
The sources describe unauthenticated remote access to sensitive administrative operations. However, the supplied record is not in KEV, and the bundle provides no evidence of active exploitation in the wild. Public researcher write-ups exist, increasing awareness, but their existence alone does not establish real-world exploitation.
Researcher notes
The core trust-boundary failure is in the dispatcher: action selection reaches privileged admin_class.php methods without an authentication or authorization gate. Reported impact includes customer creation and deletion or modification of users, tickets, departments, comments, and other records. No official patch, fixed version, reliable CPE mapping, or confirmed exploitation evidence appears in the supplied bundle.
Mitigation direction
Identify and prioritize every deployment of Customer Support System 1.0.
Restrict untrusted access to ajax.php until authoritative remediation is available.
Enforce server-side authentication and authorization before every administrative action.
Check SourceCodester guidance for an official patch or supported upgrade.
Back up application data and review administrative account recovery procedures.
Validation and detection
Confirm deployed product versions and whether ajax.php is externally reachable.
Verify every administrative AJAX action rejects unauthenticated requests.
Test authorization using non-administrative accounts without changing production data.
Review logs for unexpected customer creation, user deletion, or record modification.
Confirm administrator accounts and critical application records remain intact.
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-306: Credential and account abuse lookup
Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. 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.
CWE-862: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. 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-306 · source CWE mapping
Missing Authentication for Critical Function
Missing Authentication for Critical Function represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Missing Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.