CVE-2024-31551
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 · uneditedDirectory Traversal vulnerability in lib/admin/image.admin.php in cmseasy v7.7.7.9 20240105 allows attackers to delete arbitrary files via crafted GET request.
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 confidenceA directory traversal vulnerability in lib/admin/image.admin.php of cmseasy v7.7.7.9 allows attackers to delete arbitrary files on the server by sending crafted GET requests containing path traversal sequences (e.g., ../../) to manipulate file deletion paths.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 7.7.7.9CVSS 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
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 Cmseasy installationIdentify if the web application is Cmseasy by checking for characteristic files (e.g., index.php, license.txt, or common Cmseasy URL patterns) or by examining HTTP response headers/HTML source for Cmseasy signaturesAffected if The target is not running Cmseasy (not affected)
-
Verify exact version 7.7.7.9Check the installed Cmseasy version by inspecting version files (commonly in /config/version.php, /version, or within the admin dashboard footer), or by comparing file hashes of lib/admin/image.admin.php against the vulnerable releaseAffected if Version is not exactly 7.7.7.9 (not affected)
-
Confirm vulnerable file existsVerify that lib/admin/image.admin.php exists on the server by attempting to access it directly via HTTP (e.g., GET request to /lib/admin/image.admin.php)Affected if The file does not exist or returns a 404 (may not be affected)
-
Check admin panel accessibilityDetermine if the admin panel is network-accessible by attempting to reach the login page (commonly at /admin or /index.php?case=admin) without IP restrictions or authentication in placeAffected if The admin panel is completely blocked by firewall, IP whitelist, or other network access controls (likely not affected)
-
Verify image admin functionality is enabledCheck if the image admin module is enabled in the Cmseasy admin configuration (typically under system settings or plugin/module management), or attempt a benign request to lib/admin/image.admin.php to confirm it respondsAffected if The image admin functionality is disabled in the configuration (not affected)
The environment is affected only if running Cmseasy version exactly 7.7.7.9 with the lib/admin/image.admin.php file present and the admin panel/functionality accessible without restrictions.
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 dataApply the latest security patch from cmseasy; until then, restrict network access to the admin panel and consider disabling the image administration functionality.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-31551 — 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-31551 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