CVE-2025-25181
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.
do firstApply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
Can a WAF block it? Yes. The vulnerability is in a web application page and involves a SQL injection via a specific parameter in an HTTP request, which can be detected by looking for SQL injection patterns in that parameter. A WAF rule can match PmSess1 parameter containing SQL injection syntax. No tracked WAF vendor has published a rule for this CVE yet, so you would write it yourself.
What a custom rule would match: PmSess1 parameter containing SQL injection syntax
Also consider: patch · custom WAF rule · parameterized queries · ORM
Based on an AI reading of the CVE description, and no vendor rule found yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.
Is CVE-2025-25181 being exploited?
Yes. CVE-2025-25181 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.
How severe is CVE-2025-25181?
CVE-2025-25181 is rated Medium with a CVSS score of 5.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2025-25181?
Yes. A fix has been recorded for CVE-2025-25181. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2025-25181 affect?
CVE-2025-25181 affects advantive:veracore. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
- affected<= 2025.1.0
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.
cisa ssvc
- exploitation
- active
- automatable
- yes
- technical impact
- total
Assessed by CISA 14 Mar 2025 (SSVC 2.0.3).
timeline
- 3 Feb 2025Published
- 10 Mar 2025Added to CISA KEV (exploited in the wild) · 34 days later
- 14 Mar 2025CISA SSVC assessment: exploitation active · 4 days later
- 31 Mar 2025CISA remediation due date (US federal agencies) · 17 days later
- 26 Feb 2026CVE record last updated · 333 days (about 11 months) later
- 2 Nov 2026Analysed by vulneraibility.com · 249 days (about 8 months) later
- Linkadvantive.my.site.com /support/s/knowledge
- Linkintezer.com /blog/research/xe-group-exploiting-zero-days/
- Linksolissecurity.com /en-us/insights/xe-group-from-credit-card-skimming-to-exploiting-zero-days/
- Linkcisa.gov /known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-25181
sources
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- CISA KEV catalog: exploitation, date added, due date
- CISA Vulnrichment (ADP): SSVC decision points
- FIRST EPSS: exploit probability and percentile
- Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.