CVE-2018-15851
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 Flexo CMS v0.1.6. There is a CSRF vulnerability that can add an administrator via /admin/user/add.
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 confidenceFlexo CMS v0.1.6 is vulnerable to CSRF via the /admin/user/add endpoint. An attacker can craft a malicious page that, when visited by a logged-in administrator, silently submits a request to create a new administrator account without the admin's consent or knowledge.
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= 0.1.6CVSS 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.
-
Confirm Flexo CMS installationLocate the Flexo CMS application files in your web server directory. Common locations include /var/www/html/, /wwwroot/, or the document root of your web server.Affected if Flexo CMS is not installed on your server - you are not affected.
-
Identify the installed versionCheck the version file or header within the Flexo CMS installation. Typically found in a version.php, composer.json, or the admin dashboard footer.Affected if The installed version is 0.1.6 - proceed to next checks. If version differs, you are likely not affected.
-
Verify the user creation endpoint existsNavigate to or check for the presence of the /admin/user/add route in the Flexo CMS routing configuration or access it directly if you have admin access.Affected if The /admin/user/add endpoint does not exist - you are not affected. If it exists, you may be vulnerable.
-
Inspect user creation form for CSRF protectionAccess the /admin/user/add page as an administrator and view the HTML source. Look for a hidden input field containing a token (commonly named 'csrf_token', 'token', or 'csrf') or check if the form submission includes any anti-CSRF mechanism.Affected if The form lacks a CSRF token field and no token is submitted with the request - you are vulnerable to this CSRF attack.
You are affected if Flexo CMS version 0.1.6 is running and the /admin/user/add endpoint does not implement anti-CSRF token validation on the user creation form.
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 all state-changing admin forms including user creation, and validate these tokens server-side before processing requests. Additionally, configure SameSite cookies and consider Referer/Origin header validation as defense-in-depth.
- Consultation1.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,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-15851 — 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-15851 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