dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-22371

CRITICAL · 9.3 CVSS v4.0 Published 2025-04-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in SicommNet BASEC (SaaS Service) login page allows an unauthenticated remote attacker to Bypass Authentication and execute arbitrary SQL commands.This issue at least affects BASEC for the date of 14 Dec 2021 onwards. It is very likely that this vulnerability has been present in the solution before that. The issue was fixed by SicommNet around 11pm on 16 april 2025 (Eastern Time)

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

SQL injection vulnerability in the SicommNet BASEC SaaS login page allows unauthenticated remote attackers to bypass authentication and execute arbitrary SQL commands via improper neutralization of special elements in SQL queries.

MitigationVerify the BASEC instance has been updated with the vendor patch deployed on 16 April 2025. Review authentication logs for suspicious activity dating back to at least 14 Dec 2021 and implement web application firewall rules to detect SQL injection patterns as defense-in-depth.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
Authentication
Y
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:L/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:Y/R:X/V:C/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm you are running SicommNet BASEC SaaS
    Identify the product by reviewing your web application URL, headers, or documentation. Look for references to 'SicommNet BASEC' or 'BASEC SaaS' in your infrastructure inventory or asset management records.
    Affected if The deployed product is SicommNet BASEC SaaS with a login page accessible via web browser.
  2. Determine the installed BASEC version
    Check the vendor documentation, software inventory, or the application's 'About' or 'Help' section for the version number. Compare it to the patch released on 16 April 2025.
    Affected if The installed version predates the 16 April 2025 vendor patch.
  3. Verify the login page is internet-facing
    Determine if the BASEC login page is exposed to the public internet by reviewing firewall rules, reverse proxy configurations, or external scanning results.
    Affected if The BASEC login page is accessible from untrusted networks without VPN or IP restriction.
  4. Review authentication logs for SQL injection attempts
    Examine BASEC authentication logs, web server logs, or WAF logs for unusual patterns in the username/email field such as: single quotes ('), SQL comments (--, /*), UNION statements, OR 1=1, or other SQL syntax.
    Affected if Logs contain login attempts with SQL metacharacters or injection patterns submitted to the login form.
  5. Check for unauthorized account access
    Review authentication logs for successful logins from IP addresses that do not belong to legitimate users, or for sessions created without prior failed login attempts.
    Affected if Authentication logs show successful logins that bypassed normal credential validation or originated from suspicious sources.

You are affected if you run SicommNet BASEC SaaS with a version prior to the 16 April 2025 patch and the login page is accessible to unauthenticated users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Verify the BASEC instance has been updated with the vendor patch deployed on 16 April 2025. Review authentication logs for suspicious activity dating back to at least 14 Dec 2021 and implement web application firewall rules to detect SQL injection patterns as defense-in-depth.

Recommended fix Moderate confidence
  1. Contact SicommNet support to confirm your BASEC SaaS instance has been updated with the security fix applied on April 16, 2025
  2. Request written confirmation from SicommNet that the SQL injection vulnerability (CVE-2025-22371) has been remediated on your specific tenant
  3. If using any API integrations with BASEC, verify they still function correctly after the patch was applied

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,920
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,072.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-22371 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-22371 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data