CVE-2025-70141: n/a
Source CVE Database V5
Not known to be exploited · CVSS 9.4 Critical.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.7% chance of exploitation in 30 days – higher than 55% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 18 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.
What to do
AI-suggested
1. Immediately restrict access to ajax.php by implementing strict authentication and authorization checks to ensure only legitimate, authenticated users with appropriate privileges can invoke administrative actions. 2. Employ web application firewalls (WAFs) to detect and block suspicious requests targeting ajax.php, especially those attempting to manipulate the 'action' parameter. 3. Conduct a thorough audit of user accounts and application logs to identify any unauthorized changes or suspicious activity. 4. Isolate or temporarily disable the vulnerable functionality if feasible until a vendor patch or official fix is available. 5. Monitor network traffic for anomalous patterns indicative of exploitation attempts. 6. Engage with the software vendor or community to obtain or develop patches or updates addressing the vulnerability. 7. Implement network segmentation to limit exposure of the customer support system to untrusted networks. 8. Educate IT and security teams about this vulnerability and ensure incident response plans include scenarios involving unauthorized administrative access. 9. Regularly back up critical application data and verify backup integrity to enable recovery in case of data tampering or deletion.
Description
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.