CVE-2007-5441
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 · uneditedCMS Made Simple 1.1.3.1 does not check the permissions assigned to users in some situations, which allows remote authenticated users to perform some administrative actions, as demonstrated by (1) adding a user via a direct request to admin/adduser.php and (2) reading the admin log via an "admin/adminlog.php?page=1" request.
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 confidenceCMS Made Simple 1.1.3.1 contains an insecure direct object reference (IDOR) vulnerability where the application fails to properly enforce permission checks for authenticated users. This authorization bypass allows any authenticated user to access administrative functions—specifically adding new users via admin/adduser.php and viewing admin logs via admin/adminlog.php—regardless of their assigned privilege level.
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.1.3.1CVSS 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
- Authentication
- Single
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:S/C:P/I:P/A:P
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 versionLocate the version file or admin panel footer that displays the installed CMS Made Simple version numberAffected if The installed version is exactly 1.1.3.1
-
Verify admin/adduser.php existsCheck for the presence of the file /admin/adduser.php in the web root directoryAffected if The file exists and is accessible via the web server
-
Verify admin/adminlog.php existsCheck for the presence of the file /admin/adminlog.php in the web root directoryAffected if The file exists and is accessible via the web server
-
Check user authentication is enabledVerify that the CMS Made Simple installation has user authentication configured and activeAffected if Users can authenticate to the admin panel with any account
-
Test low-privilege user access to admin functionsLog in with a standard authenticated user (non-admin) and attempt to access /admin/adduser.php or /admin/adminlog.php directlyAffected if A standard user can access these admin pages without receiving a permission denied error
If running version 1.1.3.1 with the admin/adduser.php and admin/adminlog.php files present and accessible, any authenticated user can bypass authorization to access administrative functions.
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 dataUpgrade to a patched version of CMS Made Simple that includes proper permission validation. If immediate patching is unavailable, restrict administrative page access by IP address or disable the affected administrative endpoints until the fix can be applied.
- Consultation2.0 h
- Implementation3.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-5441 — 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-2007-5441 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