CVE-2018-10266
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 · uneditedBEESCMS 4.0 has a CSRF vulnerability to add an administrator account via the admin/admin_admin.php?nav=list_admin_user&admin_p_nav=user URI.
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 confidenceBEESCMS 4.0 is vulnerable to Cross-Site Request Forgery (CSRF) in the admin panel at admin/admin_admin.php. An attacker can craft a malicious page that, when visited by an authenticated administrator, will silently create a new administrator account without the admin's consent.
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= 4.0CVSS 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 if BEESCMS is installedLook for the BEESCMS installation directory on the web server. Check common locations such as /var/www/html/, /www/, or the web root. Look for files named admin_admin.php within an 'admin' folder.Affected if The file admin/admin_admin.php exists and belongs to BEESCMS version 4.0
-
Determine the installed BEESCms versionCheck the version information in the BEESCMS source code. Look for a version file, README, or any file containing '4.0' as the version number. Common locations include a version.php file or the main index.php in the BEESCMS root directory.Affected if The installed version is exactly 4.0 (matches = 4.0)
-
Verify the admin panel is accessibleConfirm the admin/admin_admin.php file is accessible via the web server. Attempt to access the admin login page or the specific admin_admin.php endpoint through the web browser or curl command.Affected if The admin panel at admin/admin_admin.php is reachable over the network
-
Check for anti-CSRF protection in the vulnerable fileOpen admin/admin_admin.php in a text editor or use grep to search for CSRF token validation. Look for patterns such as 'token', 'csrf', 'verify', or 'nonce' in the code. Examine form handling logic in this file to see if any token validation occurs before processing account creation requests.Affected if No anti-CSRF token validation is found in admin/admin_admin.php before processing administrator account creation
-
Check session and request validation patternsReview how the admin_admin.php handles form submissions. Look for any session-based validation or referrer checking. Search for 'session_start', '$_SESSION', '$_POST', and '$_REQUEST' to understand how administrator account creation requests are processed.Affected if The file processes POST requests to create administrator accounts without validating a unique token or checking the request origin
A user is affected if BEESCMS version 4.0 is installed and the admin/admin_admin.php file lacks anti-CSRF token validation for administrator account creation operations.
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 (synchronizer token pattern) on all admin forms and validate these tokens server-side before processing any state-changing requests.
- 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-10266 — 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-10266 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