VulnerabilityPublished 3 Feb 2025Updated 26 Feb 2026

CVE-2025-25181: Advantive VeraCore · SQL Injection

Affects Advantive VeraCoreSource CVE Database V5

Exploited in the wild · KEV due 31 Mar 2025 · 55% EPSS : apply the vendor's fix or mitigations to Advantive VeraCore now.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score

5.8Medium

How severe the flaw is on the 0–10 CVSS scale.

KEV deadline: 31 Mar 2025 US federal agencies must patch by this date; a sensible deadline for everyone else. Other KEV due dates
EPSS: 55.5% chance of exploitation in 30 days – higher than 99% 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:C/C:L/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Changed
Confidentiality: Low
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

t = 0 is the CVE’s publication on cve.org

Disclosed: evidence found.
CVE published 3 Feb 2025
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: evidence found.
Listed in CISA KEV 35 days after disclosure
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

CVE published
on cve.org
3 Feb 2025, t = 0
Added to CISA KEV (opens in a new tab)
exploitation confirmed
10 Mar 2025, 35 days after disclosure
KEV remediation due
US federal deadline
31 Mar 2025, 56 days after disclosure

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CISA KEV (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

Affected software

Product	Affected	Fixed in
Advantive VeraCore	Affected =0	Fixed in–

Description

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.

Impact

The primary impact of CVE-2025-25181 is unauthorized disclosure of sensitive data stored in the VeraCore database due to SQL injection. Attackers can remotely execute arbitrary SQL queries, potentially extracting confidential business information such as inventory data, customer details, or transaction records. Although the vulnerability does not allow data modification or service disruption, the confidentiality breach can lead to competitive disadvantage, regulatory compliance issues, and reputational damage. Organizations relying on VeraCore for supply chain management may face operational risks if sensitive data is exposed. The ease of exploitation without authentication increases the threat level, especially if the affected systems are internet-facing. However, the absence of known exploits in the wild suggests limited current exploitation. The impact is geographically dependent on VeraCore deployment, with industries in logistics, manufacturing, and distribution most affected.

Mitigation

To mitigate CVE-2025-25181, organizations should implement the following specific measures: 1) Apply any available vendor patches or updates for Advantive VeraCore immediately once released. 2) If patches are not yet available, employ web application firewalls (WAFs) with custom rules to detect and block SQL injection attempts targeting the PmSess1 parameter. 3) Conduct thorough input validation and sanitization on all user-supplied parameters, especially PmSess1, ensuring that special SQL characters are properly escaped or rejected. 4) Refactor the vulnerable code to use parameterized queries or prepared statements instead of dynamic SQL concatenation. 5) Monitor database logs and application logs for unusual query patterns or repeated failed attempts indicative of injection attacks. 6) Restrict network exposure of VeraCore management interfaces to trusted internal networks or VPNs to reduce attack surface. 7) Educate developers and administrators on secure coding practices and the risks of SQL injection. These targeted actions go beyond generic advice by focusing on the specific vulnerable parameter and the operational context of VeraCore deployments.

CWE-89Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #2OWASP Top 10 A05:2025: Injection (opens in a new tab)
The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Architecture and Design · Parameterization
If available, use structured mechanisms that automatically enforce the separation between data and code. These mechanisms may be able to provide the relevant quoting, encoding, and validation automatically, instead of relying on the developer to provide this capability at every point where output is generated.
Architecture and Design · Operation · Environment Hardening
Run your code using the lowest privileges that are required to accomplish the necessary tasks. If possible, create isolated accounts with limited privileges that are only used for a single task. That way, a successful attack will not immediately give the attacker access to the rest of the software or its environment.
OWASP Cheat Sheets
Query Parameterization (opens in a new tab)
Unvalidated Redirects and Forwards (opens in a new tab)
XML Security (opens in a new tab)
XML External Entity Prevention (opens in a new tab)
File Upload (opens in a new tab)
OWASP ASVS 4.0.3
V5.3.4 (opens in a new tab)
V5.3.5 (opens in a new tab)
V1.5.1 (opens in a new tab)
Attack patterns
Command Line Execution through SQL Injection (opens in a new tab)
Object Relational Mapping Injection (opens in a new tab)
SQL Injection through SOAP Parameter Tampering (opens in a new tab)
Expanding Control over the Operating System from the Database (opens in a new tab)
SQL Injection (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

Timeline

What to do

Affected software

Description

AI analysisMachine-generated, updated 26 Feb 2026, 23:57 UTC

WeaknessesCWE-89

Technical details

References

Community reviews

Related threats