CVE-2024-40332
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 · uneditedidccms v1.35 was discovered to contain a Cross-Site Request Forgery (CSRF) vulnerability via /admin/moneyRecord_deal.php?mudi=delRecord
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 confidenceidccms v1.35 contains a Cross-Site Request Forgery (CSRF) vulnerability in the admin panel at /admin/moneyRecord_deal.php?mudi=delRecord. An authenticated administrator visiting a malicious site could be tricked into unknowingly deleting money records due to the lack of proper request origin validation.
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= 1.35CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 idccms version is 1.35Identify the installed version of idccms in your environment through the application itself, version file, or software inventoryAffected if The installed version is exactly 1.35
-
Verify admin panel is accessibleAccess the admin panel directory at /admin/ and confirm you can reach the administrative login or interfaceAffected if The admin panel is accessible and accepts authentication
-
Check if vulnerable endpoint existsLocate the file /admin/moneyRecord_deal.php in your installation and confirm it handles the mudi=delRecord parameterAffected if The file exists and processes the delRecord action for money records
-
Inspect deletion form for CSRF tokensAccess the money record deletion interface in the admin panel, view the HTML source, and look for anti-CSRF tokens, hidden fields, or security tokens in the formAffected if No anti-CSRF token or security token is present in the deletion form
-
Verify Origin/Referer validationSend a test deletion request without a Referer header or with an external Origin header to see if the server rejects itAffected if The server accepts deletion requests without validating the request origin
You are affected if idccms version 1.35 is running, the admin panel is accessible, and the money record deletion endpoint lacks anti-CSRF tokens and server-side Origin/Referer 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 anti-CSRF tokens on the delete record form and validate the Referer or Origin header server-side to ensure requests originate from legitimate pages within the application.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-40332 — 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-40332 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