CVE-2024-1529
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 · uneditedVulnerability in CMS Made Simple 2.2.14, which does not sufficiently encode user-controlled input, resulting in a Cross-Site Scripting (XSS) vulnerability through /admin/adduser.php, in multiple parameters. This vulnerability could allow a remote attacker to send a specially crafted JavaScript payload to an authenticated user and partially take over their browser session.
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 confidenceCross-Site Scripting (XSS) vulnerability in CMS Made Simple 2.2.14 admin interface at /admin/adduser.php. Multiple parameters in the user creation form do not properly encode user-controlled input, allowing injection of malicious JavaScript that can execute in authenticated users' browsers and partially hijack their sessions.
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= 2.2.14CVSS 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.
-
Identify CMS Made Simple installationCheck for CMS Made Simple by looking for its characteristic directory structure, admin login page, or by searching for known files like /lib/ from the web root.Affected if CMS Made Simple is not installed on this system (not applicable).
-
Determine installed versionLocate the version file or check the admin footer, typically found in the admin dashboard or in a VERSION file in the installation root directory.Affected if The installed version is not 2.2.14 (only version 2.2.14 is affected).
-
Verify vulnerable file existsCheck if the file /admin/adduser.php exists in the web root. This is the file containing the XSS vulnerability.Affected if The file adduser.php does not exist or the /admin/ interface is not accessible.
-
Confirm admin access to user creation formLog into the CMS Made Simple admin interface and navigate to /admin/adduser.php or access the user creation functionality through the admin panel.Affected if You cannot access the admin interface or user creation form; the vulnerability requires an authenticated admin session to exploit.
You are affected only if your installed CMS Made Simple version is exactly 2.2.14 and you have access to the admin interface where the user creation form at /admin/adduser.php can be accessed.
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.
dbcve · scopedApply proper output encoding/escaping for all user-supplied parameters in adduser.php before rendering them in HTML context. Validate input on the server side and implement Content Security Policy headers as defense-in-depth.
Latest stable CMS Made Simple release (version 2.2.15 or later)
- 1. Backup your CMS Made Simple database and files before making any changes
- 2. Download the latest stable version of CMS Made Simple from the official repository (https://www.cmsmadesimple.org/)
- 3. Replace the existing installation files with the new version, preserving your configuration and content
- 4. Verify the /admin/adduser.php file has been updated and contains proper input encoding
- 5. Test the admin user creation functionality to confirm the XSS vulnerability is remediated
- 6. Clear all caches and sessions after the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-1529 — 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-1529 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