dbcve.org
Improper Input ValidationWeakness · CWE-20

CVE-2025-10460

CRITICAL · 9.4 CVSS v4.0 Published 2025-11-17
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
A SQL Injection vulnerability on an endpoint in BEIMS Contractor Web, a legacy product that is no longer maintained or patched by the vendor, allows an unauthorised user to retrieve sensitive database contents via unsanitized parameter input. This vulnerability occurs due to improper input validation on /BEIMSWeb/contractor.asp endpoint and successful exploitation requires a contractor.asp endpoint open to the internet. This vulnerability allows attackers to execute arbitrary SQL commands, compromising the confidentiality, integrity and potentially the availability of the database.  Version 5.7.139  has been confirmed as vulnerable. Other versions have not been confirmed by the vendor and users should assume that all versions of BEIMS Contractor Web may be impacted until further guidance is provided by the vendor.

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

A SQL Injection vulnerability exists in the /BEIMSWeb/contractor.asp endpoint of BEIMS Contractor Web. The endpoint fails to properly validate and sanitize user input, allowing unauthenticated attackers to inject arbitrary SQL commands. This can lead to unauthorized access to sensitive database contents and potential full database compromise.

MitigationSince the vendor no longer maintains this product, organizations should immediately remove the contractor.asp endpoint from internet exposure via network segmentation or firewall rules, and/or deploy a WAF with SQL injection filtering rules to block exploitation attempts.

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
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:L/SC:H/SI:L/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:X/R:X/V:X/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 BEIMS Contractor Web installation
    Search for the BEIMSWeb directory on the web server filesystem or check if the application responds to requests at /BEIMSWeb/
    Affected if The BEIMS Contractor Web application is installed and running on the server
  2. Verify vulnerable endpoint exists
    Attempt to access the endpoint /BEIMSWeb/contractor.asp via HTTP/HTTPS request and confirm it returns a response (even an error)
    Affected if The /BEIMSWeb/contractor.asp endpoint exists and is reachable
  3. Assess network exposure
    Determine if the server hosting the endpoint is accessible from untrusted networks (internet-facing) by reviewing firewall rules, ACLs, or network boundary configurations
    Affected if The endpoint is accessible from untrusted/network-facing interfaces without authentication
  4. Inspect web server logs for SQL injection attempts
    Review web server access logs (IIS, Apache) for requests to /BEIMSWeb/contractor.asp containing SQL metacharacters such as ', UNION, SELECT, DROP, or common injection patterns in query parameters
    Affected if Log analysis reveals suspicious SQL injection patterns targeting the contractor.asp endpoint
  5. Check database audit logs for unauthorized queries
    Review database audit logs or transaction logs for unexpected or unauthorized SQL commands executed from the web application service account, particularly commands accessing sensitive tables
    Affected if Database logs show unauthorized or unexpected SQL commands originating from the application

A user is affected if BEIMS Contractor Web is installed and the /BEIMSWeb/contractor.asp endpoint is accessible, particularly from untrusted networks, as the SQL injection can be exploited without authentication.

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

Since the vendor no longer maintains this product, organizations should immediately remove the contractor.asp endpoint from internet exposure via network segmentation or firewall rules, and/or deploy a WAF with SQL injection filtering rules to block exploitation attempts.

Recommended fix High confidence
  1. Since this is a legacy product that is no longer maintained or patched by the vendor, there is no vendor-provided fix available.
  2. If this endpoint is still in use, immediately restrict network access to prevent external attackers from reaching the /BEIMSWeb/contractor.asp endpoint.
  3. Consider deploying a Web Application Firewall (WAF) in front of this endpoint if it must remain internet-accessible for legitimate business purposes.
  4. Evaluate migration to an actively maintained alternative solution, as the vendor has confirmed this product will not receive security updates.
  5. If the endpoint is not required for business operations, disable or remove the BEIMS Contractor Web application entirely.
Caveat No upgrade path available - vendor has confirmed this product is legacy and unmaintained; no patched version exists

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

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-10460 — 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-10460 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