CVE-2018-15568
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 · uneditedtp5cms through 2017-05-25 has CSRF via admin.php/category/delete.html.
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 confidencetp5cms through 2017-05-25 contains a Cross-Site Request Forgery (CSRF) vulnerability in the admin panel. The endpoint admin.php/category/delete.html lacks anti-CSRF token validation, allowing authenticated administrators to be tricked into unintentionally deleting categories via maliciously crafted web pages.
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<= 2017-05-25CVSS 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.
-
Determine Tp5cms versionLocate the version file or header in the Tp5cms installation directory (commonly version.php, a README, or within core application files). Compare the build date or version number against the affected range: any version dated 2017-05-25 or earlier.Affected if The installed version is dated 2017-05-25 or earlier, or the version number is at or below the last vulnerable release.
-
Confirm admin panel is accessibleVerify that the web server hosts the Tp5cms admin interface and the path admin.php is reachable over HTTP/HTTPS.Affected if The admin panel at admin.php is accessible without authentication restrictions, allowing potential attackers to target authenticated administrators.
-
Locate the category delete endpointNavigate to or locate the file handling the route admin.php/category/delete.html within the application source code.Affected if The file handling admin.php/category/delete.html exists in the codebase.
-
Inspect for anti-CSRF token validationOpen the controller or handler script for the category delete function and search for anti-CSRF token validation logic (commonly checks for a token parameter, session token comparison, or use of a CSRF protection library).Affected if The category delete handler contains NO code that validates an anti-CSRF token, synchronizer token, or similar protection mechanism before processing the delete request.
A user is affected if they run Tp5cms version 2017-05-25 or earlier AND the admin panel is accessible AND the category delete endpoint lacks anti-CSRF token validation logic in its source code.
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 synchronizer token pattern (anti-CSRF tokens) on all state-changing admin operations including the category delete function, and validate Origin/Referer headers server-side as an additional defense layer.
- Consultation3.0 h
- Implementation6.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-15568 — 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-15568 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