CVE-2025-25181
SQLi in Advantive Veracore ≤ 2025.1.1.3
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:NSummary
CVE-2025-25181 is a medium-severity SQL Injection (CWE-89) vulnerability in Advantive Veracore. Its CVSS base score is 5.8 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked in the top 1% of CVEs by exploit likelihood; CISA has added it to the Known Exploited Vulnerabilities catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
A SQL injection vulnerability exists in the timeoutWarning.asp endpoint of Advantive VeraCore through version 2025.1.0. The flaw, tracked as CVE-2025-25181 and assigned CWE-89, permits remote attackers to supply arbitrary SQL commands through the PmSess1 parameter. It carries a CVSS 3.1 score of 5.8 reflecting network attack vector, low complexity, and no required privileges or user interaction, with limited confidentiality impact across a changed scope.
Unauthenticated remote attackers can exploit the injection to execute arbitrary SQL commands against the underlying database. Successful exploitation allows extraction of limited data without affecting integrity or availability.
Vendor guidance is referenced in Advantive’s support knowledge base, while CISA lists the CVE in its Known Exploited Vulnerabilities catalog, indicating that patches or configuration mitigations should be obtained from those sources and applied promptly.
The vulnerability is confirmed to be under active exploitation in the wild. Its EPSS score rose materially after disclosure, reaching a peak of 0.8169 on 2025-12-11 before receding to the current value of 0.7205, indicating sustained attacker interest.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-4072
Vulnerability Data
A SQL injection vulnerability in timeoutWarning.asp in Advantive VeraCore through 2025.1.0 allows remote attackers to execute arbitrary SQL commands via the PmSess1 parameter.
- CWE(s)
- KEV Date Added
- 10 March 2025
Related Threats
Threat-Actor AttributionAI
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V6.2.5
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and evaluation can discover SQLi flaws before deployment but does not stop their introduction.
Input validation directly stops untrusted data from reaching SQL query construction without neutralization.
Secure engineering principles require parameterized queries and input sanitization that structurally eliminate SQLi.
System monitoring can identify attempted SQLi exploitation via anomalous queries after the weakness exists.
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.
Secure SDLC practices directly target injection flaws during coding and review so largely prevent CWE-89 introduction, yet the single broad outcome leaves residual risk from incomplete neutralization techniques or missed edge cases.
Training raises developer awareness of SQLi risks and can reduce introduction likelihood (partial) but removes none of the actual coding flaw's risk by itself since technical neutralization is still required.
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.
The same secure-coding and static-analysis activities surface missing neutralization of SQL metacharacters before the system is accepted.
Early warnings and shared best-practice information help organizations apply the latest remediation techniques against SQL-injection vulnerabilities.
Threat-intelligence feeds that surface new SQL-injection campaigns enable rapid updates to query-construction defenses and detection signatures before exploitation occurs.
Secure-coding rules and security testing phases mandate the use of parameterized queries or equivalent escaping, preventing the construction of dynamic SQL statements from untrusted input.
Language-specific secure coding rules, peer review and SAST together prevent the construction of SQL statements from untrusted data without proper parameterization or escaping.