CVE-2025-40985
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 · uneditedSQL injection vulnerability in SCATI Vision Web of SCATI Labs from version 4.8 to 7.2. This vulnerability allows an attacker to exfiltrate some data from the database via the ‘login’ parameter in the endpoint ‘/scatevision_web/index.php/loginForm’.
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 confidenceSQL injection vulnerability in SCATI Vision Web allows remote attackers to inject malicious SQL queries through the 'login' parameter at the /scatevision_web/index.php/loginForm endpoint, enabling unauthorized database access and data exfiltration.
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
- High
- Privileges
- None
- Authentication
- X
- User interaction
- None
- Scope
- X
CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:N/VA:H/SC:N/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: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 checksWork through these to decide whether this CVE applies to you.
-
Locate SCATI Vision Web installationSearch for the scatevision_web directory on the server. Common web root locations include /var/www/, /www/html/, /home/*/public_html/ on Linux/Unix, or C:\inetpub\wwwroot\ on Windows. Confirm the presence of index.php within the scatevision_web folder.Affected if The SCATI Vision Web application directory (scatevision_web) exists on the server
-
Determine installed versionExamine version information within the SCATI Vision Web installation. Check for files such as VERSION.txt, version.php, or inspect index.php for a version string. Compare the found version against the affected range (versions 7.2 and below are vulnerable).Affected if The installed version is 7.2 or lower, or no version file can be located to confirm otherwise
-
Confirm loginForm endpoint is accessibleVerify the /scatevision_web/index.php/loginForm endpoint is reachable. Use a web browser or command-line tool (curl -I https://target/scatevision_web/index.php/loginForm) to confirm the endpoint responds.Affected if The loginForm endpoint returns a valid HTTP response and is accessible to attackers
-
Check input validation on login parameterReview application source code handling the login parameter at the loginForm endpoint. Inspect the authentication logic in index.php or related auth modules for use of parameterized queries (prepared statements) or input sanitization functions. The vulnerability exists if raw SQL queries are constructed using the login parameter without validation.Affected if The login parameter is used in SQL queries without prepared statements or input sanitization
The environment is affected if SCATI Vision Web is present with version 7.2 or lower, the loginForm endpoint is exposed, and the login parameter lacks parameterized queries or input validation in the authentication code.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataUpgrade to a version beyond 7.2 or apply vendor patch; until then, implement strict input validation on the login parameter and consider deploying a WAF to filter SQL injection attempts.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-40985 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-40985 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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