CVE-2018-15564
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 · uneditedAn issue was discovered in daveismyname simple-cms through 2014-03-11. There is a CSRF vulnerability that can delete any page via admin/?delpage=8.
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 Request Forgery (CSRF) vulnerability in simple-cms allows remote attackers to delete arbitrary pages by tricking authenticated administrators into visiting a malicious URL. The vulnerable endpoint admin/?delpage= lacks anti-CSRF token validation, enabling unauthorized state-changing requests.
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<= 2014-03-11CVSS 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.0/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.
-
Identify Simple Cms versionLocate the Simple Cms installation directory and check version.php, CHANGELOG, or any version file for the exact version number. Common paths include the root directory or a /includes folder.Affected if The installed version is dated 2014-03-11 or earlier, or the version number is not clearly newer.
-
Confirm admin interface existsNavigate to the /admin/ path of the Simple Cms installation in a web browser and verify the admin panel is accessible and requires authentication.Affected if The admin panel is accessible and uses simple-cms authentication.
-
Locate the page deletion endpointAccess the admin panel and identify the page deletion functionality. Look for the admin/?delpage= endpoint or equivalent page deletion mechanism in the admin interface.Affected if The admin panel contains a page deletion feature accessible via admin/?delpage= or similar URL parameter.
-
Check for anti-CSRF token presenceInspect the HTML source of the admin page deletion form or request the admin page and examine if a CSRF token, anti-CSRF token, or security token field is present in the deletion request.Affected if No anti-CSRF token is present in the page deletion form or request, and the deletion works without a token.
A user is affected if they run Simple Cms version 2014-03-11 or earlier and the admin page deletion endpoint lacks CSRF token 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 for all state-changing admin operations, particularly the page deletion functionality. Additionally, validate the Origin/Referer headers and require POST requests instead of GET for deletions.
- Consultation1.0 h
- Implementation2.0 h
- Testing1.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 $1,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-15564 — 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-2018-15564 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