CVE-2018-6844
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 1.8.14 has XSS via the Title or Description field on the Edit Forum screen.
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 confidenceMyBB 1.8.14 contains a stored Cross-Site Scripting (XSS) vulnerability in the Edit Forum screen. The Title and Description fields do not properly sanitize user input, allowing an attacker to inject malicious JavaScript code that will execute when other users view the forum.
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.14CVSS 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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
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 MyBB installation versionAccess the admin control panel and navigate to Tools & Maintenance > System Info, or check the version.php file in the MyBB root directory. The version number is displayed in the system information page.Affected if The installed version is exactly 1.8.14 (this specific version is vulnerable; later versions 1.8.15+ contain the fix)
-
Verify admin/user forum editing accessCheck if any user accounts have permission to access the Admin CP > Forums & Posts > Forum Management section, or if forum moderators have access to edit forum properties.Affected if Users with forum editing privileges exist in the system; the vulnerability is exploitable through the Edit Forum interface
-
Inspect forum database records for XSS payloadsQuery the mybb_forums table (or equivalent) in the database for suspicious patterns in the 'name' and 'description' fields. Look for HTML tags, script elements, or event handlers (e.g., <script>, onerror=, onload=, javascript:).Affected if Any forum records contain unsanitized HTML or JavaScript in title/name or description fields, indicating the vulnerability may have been exploited
You are affected if your MyBB installation is exactly version 1.8.14 and users with forum editing capabilities can access the Edit Forum screen.
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 dataUpgrade to MyBB 1.8.15 or later, or apply the vendor patch which adds proper input validation and output encoding for the Title and Description fields in the forum editing functionality.
- Consultation2.0 h
- Implementation3.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-6844 — 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-6844 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