Skip to main content
Mallory
HighExploited in the wildCISA KEVPublic exploitVulnerability

CVE-2025-25181: Unauthenticated SQL Injection in Advantive VeraCore

Published Feb 3, 2025 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS7.5High · v3.1
EPSS54.8%99th percentile
CISA KEVYesAdded Mar 10, 2025
In the wildActivePer CISA KEV
Vendor
Advantive
IdentifiersCVE-2025-25181CWE-89 · Improper Neutralization of Special…

CVE-2025-25181 is a SQL injection vulnerability affecting Advantive VeraCore through version 2025.1.0. Insufficient sanitization of the PmSess1 parameter in the session-timeout warning component allows unauthenticated remote attackers to submit crafted requests that execute arbitrary SQL commands against the application's database. Exploitation can expose, modify, or delete database data and potentially give attackers control over the affected application. The vulnerability has been actively exploited, including in a chain with CVE-2024-57968 used by XE Group to deploy ASPXSpy webshells.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation permits arbitrary SQL execution within the application's database, potentially compromising database confidentiality and integrity through unauthorized reading and modification, and causing data loss through deletion. Application takeover is also a reported potential outcome. Exploitation chained with the separate file-upload vulnerability CVE-2024-57968 has enabled webshell deployment and persistent backdoor access; those outcomes should not be attributed to this SQL injection alone.

Mitigation

If you can’t patch tonight, do this now.

Review network and security logs for evidence of exploitation or webshell activity. Network segmentation and restrictive access controls can reduce exposure but are not established fixes for this vulnerability. No vulnerability-specific vendor workaround is identified.

Remediation

Patch, then assume compromise.

No vendor update for CVE-2025-25181 was available at the time of the supplied reporting. Current patch availability is not established. Upgrading to VeraCore 2024.4.2.1 was recommended for CVE-2024-57968, not as a fix for CVE-2025-25181.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
AdvantiveVeracoreapplication
FAQ

Frequently asked questions

Is CVE-2025-25181 exploited in the wild?
Yes. As of Oct 9, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on Mar 10, 2025.
Is there a public exploit for CVE-2025-25181?
Yes. As of Oct 9, 2026, Mallory has reports of a public exploit for CVE-2025-25181.
Is there a patch for CVE-2025-25181?
No vendor update for CVE-2025-25181 was available at the time of the supplied reporting. Current patch availability is not established.
What products are affected by CVE-2025-25181?
Advantive Veracore.
How severe is CVE-2025-25181?
CVE-2025-25181 has a CVSS v3.1 score of 7.5 (High) and an EPSS score of 54.8% (99th percentile) as of Oct 9, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidence1Every report linking this CVE to a named adversary.
Associated malware1Malware families linked to this CVE, with evidence and IOCs.
Detection signatures2YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.