CVE-2024-48700
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 · uneditedKliqqi-CMS has a background arbitrary code execution vulnerability that attackers can exploit to implant backdoors or getShell via the edit_page.php component.
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 confidenceKliqqi-CMS contains an arbitrary code execution vulnerability in the edit_page.php component. Attackers can exploit this to execute arbitrary code on the server and potentially gain shell access. The vulnerability is described as a 'background' execution issue, suggesting it may involve insufficient validation of user-supplied input in page editing functionality.
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<= 3.5.2CVSS 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
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
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 Kliqqi-CMS installationSearch for Kliqqi-CMS files on the server, typically found in web root directories. Look for characteristic Kliqqi folders or files such as index.php with Kliqqi branding.Affected if Kliqqi-CMS is present on the server
-
Check installed Kliqqi versionLocate the version file or check version information within the Kliqqi installation. Common locations include a version.php file, a config file, or the admin dashboard version display.Affected if The installed version is 3.5.2 or any version lower than 3.5.2
-
Verify edit_page.php existsLocate the edit_page.php file within the Kliqqi installation directory, typically found in the admin or includes folder. Check if the file is present on the filesystem.Affected if edit_page.php exists in the Kliqqi installation
-
Check access to edit_page.php componentReview web server access logs for requests to edit_page.php. Determine if the file is accessible via HTTP/HTTPS without proper authentication restrictions.Affected if edit_page.php is accessible without administrative authentication or access controls are weak
-
Inspect for unauthorized modificationsCompare the edit_page.php file against a known clean installation of the same version. Look for unexpected code, suspicious function calls, or base64-encoded strings that may indicate injected code.Affected if edit_page.php has been modified from the original or contains suspicious code patterns
If Kliqqi-CMS version 3.5.2 or lower is installed with the edit_page.php component accessible, the environment is likely affected by this vulnerability.
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 dataRestrict administrative access to the edit_page.php component, implement strict input validation and sanitization on all page editing parameters, and consider deploying a WAF rule to block suspicious requests to this endpoint until a patch can be applied.
- 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-48700 — 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-48700 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