CVE-2024-25320: SQL Injection
Source CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 26 Oct 2026, 08:30 UTC
- EPSS
- 0.7% chance of exploitation in 30 days – higher than 54% 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:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 16 Feb 2024
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 26 Oct 2026.
What to do
AI-suggested
Until official patches are released, organizations should implement the following mitigations: 1) Deploy web application firewalls (WAFs) with rules specifically designed to detect and block SQL injection attempts targeting the $AFF_ID parameter and /affair/delete.php endpoint. 2) Apply strict input validation and sanitization on all user-supplied parameters, especially $AFF_ID, to reject or neutralize malicious input. 3) Restrict access to the /affair/delete.php script by IP whitelisting or network segmentation to limit exposure. 4) Monitor database logs and application logs for unusual queries or error messages indicative of injection attempts. 5) Conduct thorough security assessments and penetration testing focused on SQL injection vectors within Tongda OA deployments. 6) Prepare for rapid deployment of official patches once available and maintain an incident response plan for potential exploitation. 7) Educate administrators and users about the risks and signs of SQL injection attacks to enhance detection and response capabilities.
Description
Tongda OA v2017 and up to v11.9 was discovered to contain a SQL injection vulnerability via the $AFF_ID parameter at /affair/delete.php.