CVE-2024-46372
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 · uneditedDedeCMS 5.7.115 is vulnerable to Cross Site Scripting (XSS) via the advertisement code box in the advertisement management module.
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 confidenceDedeCMS 5.7.115 contains a stored Cross Site Scripting (XSS) vulnerability in the advertisement management module. The vulnerability exists within the advertisement code box functionality where unsanitized user-supplied input is rendered, allowing execution of malicious JavaScript in the context of other users' browsers.
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= 5.7.115CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 DedeCMS versionLocate and inspect the version file or admin panel version indicator in your DedeCMS installation. Common locations include a version.php file or the system information page in the admin dashboard.Affected if Your installed version matches 5.7.115 exactly.
-
Verify advertisement module is accessibleCheck if the advertisement management module is enabled and accessible in your DedeCMS admin panel. Look for the ads or advertisement management section in the navigation.Affected if The advertisement management module is present and accessible in your installation.
-
Identify advertisement code box entriesAccess the advertisement management interface and review any configured advertisements, specifically looking for entries that use the code box or custom code functionality.Affected if You have advertisements configured that utilize the code box or custom code input feature.
-
Inspect advertisement data for unsanitized contentExamine the stored advertisement code entries directly in the database or through the admin interface. Look for any HTML, JavaScript, or script tags that were input into the code box fields without visible sanitization.Affected if The stored advertisement code contains raw HTML, JavaScript, or script tags that could execute in a user's browser.
You are affected if your DedeCMS installation is version 5.7.115 and contains advertisements using the code box feature with unsanitized JavaScript or HTML content that could execute in user browsers.
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 proper input validation and output encoding/escaping on all user-supplied data in the advertisement code box. Apply context-appropriate sanitization (e.g., HTML entity encoding) before rendering user input in web pages.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-46372 — 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-46372 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