CVE-2024-11992
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 · uneditedAbsolute path traversal vulnerability in Quick.CMS, version 6.7, the exploitation of which could allow remote users to bypass the intended restrictions and download any file if it has the appropriate permissions outside of documentroot configured on the server via the aDirFiles%5B0%5D parameter in the admin.php page. This vulnerability allows an attacker to delete files stored on the server due to a lack of proper verification of user-supplied input.
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 confidenceAbsolute path traversal vulnerability in Quick.CMS v6.7 where the aDirFiles%5B0%5D parameter in admin.php lacks proper input validation, allowing attackers to use absolute file paths to download or delete any file on the server accessible with the web server's permissions, regardless of documentroot restrictions.
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
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
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.
-
Confirm Quick.CMS installationIdentify Quick.CMS by locating typical files such as admin.php, index.php, or config.php in the web root. Check page footers or HTML source for 'Quick.CMS' branding.Affected if Quick.CMS is present on this server
-
Determine installed versionOpen the file includes/license.php or similar version definition file within the Quick.CMS installation directory. Read the version number defined there.Affected if Version is 6.7 or an unpatched release
-
Verify admin.php is accessibleAttempt to access the admin.php script via HTTP/HTTPS request. Determine if the script is reachable with or without authentication.Affected if admin.php endpoint responds and is accessible
-
Confirm aDirFiles[0] parameter existsLocate the admin.php source code and search for references to aDirFiles array parameter. Verify the parameter is used in file operations.Affected if admin.php contains code handling aDirFiles[0] parameter for file operations
-
Check file operation logicReview the admin.php code around aDirFiles[0] usage. Determine if absolute file paths can be passed directly to file system operations without validation or path normalization.Affected if aDirFiles[0] accepts absolute paths without validation or sanitization checks
Environment is affected if running Quick.CMS version 6.7 or unpatched, with accessible admin.php where the aDirFiles[0] parameter accepts absolute paths without proper validation.
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 dataImplement strict input validation to restrict file paths to within the configured document root, deny absolute paths, and validate all file operations against an allowed directory whitelist; consider upgrading to a patched version when available.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-11992 — 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-2024-11992 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