Threats / Advantive / CVE-2025-25181
CVE-2025-25181
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
Advantive VeraCore vulnerability
Advantive VeraCore contains a SQL injection vulnerability in timeoutWarning.asp via the PmSess1 parameter, allowing remote attackers to execute arbitrary SQL commands.
Verdict
Today item — known-exploited.
A SQL injection flaw in VeraCore's timeoutWarning.asp enables unauthenticated remote code execution through the PmSess1 parameter. The vulnerability is actively exploited in the wild with high EPSS probability, posing immediate risk to database integrity and confidentiality.
CISA KEV Yes · 2025-03-105EPSS 0.50863 (verify live)6CVSS 5.83CISA SSVC Exploitation: active · Automatable: yes · Impact: total4
01
Is it exploitable?
— the evidence, ranked above the scoreReported exploitation
4 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2025-03-10).
Probability (EPSS)
EPSS 0.50863 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 5.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N) · Affected: Advantive, VeraCore. Confirm exact fixed builds in the vendor advisory.CVSS — CNA-assigned (CVE.org), version 3.1, set at disclosure.
Weakness (CWE)
Mapped to CWE-89 SQL Injection — weakness family: Injection.CWE — CNA-assigned (CVE.org); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: yes · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 35 days after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I craft a malicious HTTP request containing SQL metacharacters in the PmSess1 parameter to probe the application's input validation.
Business
Attackers gain direct access to the underlying database without authentication, enabling data exfiltration or manipulation.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I inject SQL commands that extract sensitive data such as user credentials, patient records, or financial information from the database.
Business
Confidential business and customer data is compromised, triggering regulatory violations and reputational damage.
3
Lateral reach — past segmentation narrative 3
Attacker
I execute SQL statements to modify or delete critical records, or escalate privileges within the application.
Business
Data integrity is compromised, operational continuity is disrupted, and system availability may be degraded.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05