CVE-2018-1000502
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 · uneditedMyBB Group MyBB contains a File Inclusion vulnerability in Admin panel (Tools and Maintenance -> Task Manager -> Add New Task) that can result in Allows Local File Inclusion on modern PHP versions and Remote File Inclusion on ancient PHP versions. This attack appear to be exploitable via Must have access to admin panel. This vulnerability appears to have been fixed in 1.8.15.
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 confidenceMyBB contains a file inclusion vulnerability in the Admin panel's Task Manager (Add New Task) functionality. The flaw allows authenticated administrators to include arbitrary files, resulting in Local File Inclusion on modern PHP versions and potentially Remote File Inclusion on older PHP versions. Exploitation requires admin panel access, which limits the attack surface but still poses significant risk due to the potential for code execution and system compromise.
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.8.15CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:H/UI:N/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 MyBB versionCheck the version.php file in your MyBB root directory or view the admin panel footer which displays the version numberAffected if The installed version is below 1.8.15 (for example, 1.8.14, 1.8.13, etc.)
-
Determine if admin accounts existQuery your database for users with admin privileges (typically in the mybb_users table where usergroup ID corresponds to administrators)Affected if Any administrator-level account exists in the system, as admin access is required to reach the vulnerable Task Manager functionality
-
Verify admin panel accessibilityConfirm that the admin panel (typically at /admin/index.php) is accessible and not restricted by network-level controls or IP allowlistingAffected if The admin panel can be reached by any authenticated administrator user
-
Check PHP versionRun php -v from command line or use phpinfo() to determine the PHP version running MyBBAffected if Running PHP versions below 5.x may allow Remote File Inclusion; modern PHP versions (5.x and above) limit exploitation to Local File Inclusion only
Your environment is affected if you are running any MyBB version below 1.8.15 and have at least one administrator account with access to the admin panel Task Manager functionality.
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 data1.8.15
Upgrade to MyBB version 1.8.15 or later which contains the fix. Prior to patching, strictly limit admin panel access to trusted personnel only and monitor for suspicious activity.
- Consultation3.0 h
- Implementation2.0 h
- Testing4.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,072.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-1000502 — 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-1000502 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