dbcve.org
Code InjectionWeakness · CWE-94

CVE-2026-11860

HIGH · 7.5 CVSS v4.0 Published 2026-06-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
No privileges

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
Quick.CMS deserializes user-controlled data received over plaintext HTTP without ensuring integrity or authenticity. This allows attackers to tamper with serialized payloads in transit and inject malicious objects. Because deserialization is performed without proper validation or class restrictions, crafted payloads can trigger dangerous magic methods (e.g., __wakeup() and __destruct()) and leverage gadget chains, resulting in arbitrary code execution. Exploitation is triggered automatically when an administrator accesses the admin panel. When successfully exploited, this vulnerability allows attackers to execute arbitrary code on the server via manipulated serialized data transmitted over an unprotected channel. This issue was mitigated by limiting the communication to HTTPS in a patch for version 6.8 published on 14.05.2026, deployments without this patch remain 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 · high confidence

Quick.CMS deserializes user-controlled PHP objects received over unencrypted HTTP without class restrictions or integrity checks. An attacker performing a man-in-the-middle attack can modify serialized payloads in transit, triggering magic methods like __wakeup() and __destruct() to execute gadget chains and achieve arbitrary code execution. The attack auto-triggers when an administrator accesses the admin panel.

MitigationEnforce HTTPS across all Quick.CMS deployments to prevent tampering of serialized data in transit. Additionally, refactor the codebase to replace unsafe unserialize() calls with json_decode() or implement a strict allowlist of allowed classes.

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
Adjacent
Complexity
Low
Privileges
None
Authentication
X
User interaction
P
Scope
X

CVSS:4.0/AV:A/AC:L/AT:P/PR:N/UI:P/VC:H/VI:H/VA:H/SC:L/SI:L/SA:L/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 Quick.CMS installation
    Look for Quick.CMS files in the web root, typically in a directory named 'quickcms' or check for files like 'index.php' containing 'Quick.CMS' in the source code or footer.
    Affected if Quick.CMS is present on the server
  2. Identify installed Quick.CMS version
    Open the file 'config/general.php' or 'Core.php' and look for a version variable (e.g., $config['version'] or define('VERSION', '...')). Alternatively, check the admin panel footer for the version number.
    Affected if The installed version is earlier than 6.8 (e.g., 6.7, 6.6, earlier versions)
  3. Check if HTTPS is enforced for admin access
    Inspect the server configuration (e.g., .htaccess, vhost config) and Quick.CMS configuration files for HTTPS redirect rules. Look for 'RewriteCond %{HTTPS} off' or similar directives.
    Affected if HTTP (port 80) is still accessible and no redirect to HTTPS exists, allowing MITM tampering of serialized data
  4. Verify admin panel accessibility
    Access the admin panel URL (typically /admin/ or /sxxxxxxxxx/) via HTTP to confirm it loads without forced HTTPS redirection.
    Affected if The admin panel loads over HTTP without redirecting to HTTPS

A user is affected if Quick.CMS version is earlier than 6.8 and the admin panel or serialized data is accessible over unencrypted HTTP, allowing in-transit tampering of deserialized payloads.

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

Enforce HTTPS across all Quick.CMS deployments to prevent tampering of serialized data in transit. Additionally, refactor the codebase to replace unsafe unserialize() calls with json_decode() or implement a strict allowlist of allowed classes.

Recommended fix Moderate confidence

Quick.CMS v6.8

  1. 1. Upgrade Quick.CMS to version 6.8 or later, which was published on 14.05.2026 and includes the security patch
  2. 2. After upgrading, verify that the application is configured to use HTTPS exclusively
  3. 3. Ensure the web server (Apache/Nginx) is configured to redirect all HTTP traffic to HTTPS
  4. 4. Verify that the admin panel is only accessible over HTTPS
  5. 5. Test that the deserialization vulnerability is no longer exploitable over plaintext HTTP

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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