dbcve.org
DedecmsApplication

CVE-2024-3148

HIGH · 8.8 CVSS v3.1 Published 2024-04-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/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 vulnerability, which was classified as critical, has been found in DedeCMS 5.7.112. This issue affects some unknown processing of the file dede/makehtml_archives_action.php. The manipulation leads to sql injection. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used. The associated identifier of this vulnerability is VDB-258923. NOTE: The vendor was contacted early about this disclosure but did not respond in any way.

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

SQL injection vulnerability in DedeCMS 5.7.112 within the file dede/makehtml_archives_action.php allows remote attackers to manipulate SQL queries via unknown input vectors. The vulnerability is exploitable remotely with publicly available exploit code, giving attackers the ability to execute arbitrary SQL commands against the database.

MitigationApply input validation and parameterized queries to all database interactions in makehtml_archives_action.php; audit other PHP files for similar SQL injection patterns; implement a WAF rule as a temporary protective measure until a vendor patch is available.

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
DedecmsApplication
Affected:= 5.7.112

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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 checks

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

  1. Confirm DedeCMS installation and version
    Check for DedeCMS (织梦CMS) by looking for common installation paths (/, /dede/, /uploads/) and examine version files such as include/common.inc.php or /data/admin/ver.txt for version string '5.7.112'
    Affected if Your DedeCMS version is exactly 5.7.112
  2. Verify vulnerable file exists
    Check if the file dede/makehtml_archives_action.php exists in your web root. This file handles archive HTML generation and contains the vulnerable code.
    Affected if The file /dede/makehtml_archives_action.php exists on your server
  3. Check if admin directory is web-accessible
    Verify whether the /dede/ directory (default admin path) is exposed on the web. Attempt to access it from a browser or use a tool like curl: curl -I http://your-site/dede/
    Affected if The /dede/ admin directory is accessible without authentication or uses default/weak credentials
  4. Test for the SQL injection parameter
    Review the makehtml_archives_action.php source code for unprotected parameters passed to SQL queries. If live testing is authorized, use a tool like sqlmap against suspected parameters (e.g., in the archive ID or channel ID fields).
    Affected if You can inject SQL syntax into parameters handled by makehtml_archives_action.php and observe SQL errors or unexpected behavior
  5. Check database user privileges
    Review your database configuration file (include/dedesql.php or data/common.inc.php) to determine the database user privileges assigned to the application.
    Affected if The DedeCMS database user has excessive privileges (such as DROP, CREATE, or FILE privileges) beyond SELECT, INSERT, UPDATE, DELETE

You are affected if you are running DedeCMS version 5.7.112 with the dede/makehtml_archives_action.php file accessible via the web.

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

Apply input validation and parameterized queries to all database interactions in makehtml_archives_action.php; audit other PHP files for similar SQL injection patterns; implement a WAF rule as a temporary protective measure until a vendor patch is available.

Fix this in Dedecms Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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