dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-12465

HIGH · 8.6 CVSS v4.0 Published 2025-12-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
92/100
Remediation priority · Urgent
Remotely reachable 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 Blind SQL injection vulnerability has been identified in QuickCMS. Improper neutralization of input provided by a high-privileged user into aFilesDelete allows for Blind SQL Injection attacks. The vendor was notified early about this vulnerability, but didn't respond with the details of vulnerability or vulnerable version range. Only version 6.8 was tested and confirmed as vulnerable, other versions were not tested and might also be vulnerable.

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 · moderate confidence

A Blind SQL injection vulnerability exists in QuickCMS where input to the aFilesDelete parameter is not properly neutralized when handled from high-privileged user accounts. Since it's a blind SQLi, attackers infer TRUE/FALSE conditions from application behavior rather than seeing direct database output, enabling data exfiltration through inference-based techniques.

MitigationImplement parameterized queries (prepared statements) for all database operations involving the aFilesDelete parameter, and apply context-aware input validation. Until a vendor patch is available, restrict high-privileged access to this function and monitor for suspicious query patterns.

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

CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:L/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 checks

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

  1. Confirm QuickCMS installation
    Identify QuickCMS by checking for its characteristic files (such as quickcms.php, admin/index.php, or specific QuickCMS templates/assets in the web root). Inspect page footers or admin headers for 'QuickCMS' branding.
    Affected if The software is QuickCMS and the aFilesDelete feature is present in the codebase.
  2. Determine QuickCMS version
    Locate the version file or header in the QuickCMS installation (commonly found in includes/config.php, version.txt, or the admin dashboard footer). Compare your installed version against any known version releases.
    Affected if The installed version has not received a patch for CVE-2025-12465.
  3. Locate aFilesDelete parameter handling
    Search the source code for 'aFilesDelete' in PHP files within the QuickCMS installation. Focus on files in the admin or file management modules. Examine how this parameter is processed in the database query logic.
    Affected if The aFilesDelete parameter is directly concatenated into SQL queries without parameterization.
  4. Verify high-privileged access exists
    Check user role definitions and access control files. Determine if standard or low-privileged users can access the aFilesDelete functionality, or if it requires admin/root-level privileges.
    Affected if High-privileged (administrator) accounts can access and trigger the aFilesDelete function.
  5. Inspect database query construction
    Review PHP files handling aFilesDelete for SQL query patterns. Look for direct string interpolation or concatenation of the aFilesDelete value into WHERE or DELETE statements.
    Affected if SQL queries incorporate the aFilesDelete parameter without using prepared statements or binding.

If QuickCMS is installed, the aFilesDelete parameter exists in the codebase, and SQL queries use direct parameter insertion without prepared statements, the environment is likely affected by this blind SQL injection.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement parameterized queries (prepared statements) for all database operations involving the aFilesDelete parameter, and apply context-aware input validation. Until a vendor patch is available, restrict high-privileged access to this function and monitor for suspicious query patterns.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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