Security readout for executives and security teams
Plain-English summary
A trusted forum moderator could put malicious content into a ban reason, and that content runs when the ban list page is viewed. The issue matters for forums using the MyBB Ban List plugin 1.0, especially where moderator accounts are numerous, shared, or less tightly controlled.
Executive priority
Treat this as a targeted forum integrity risk, not a broad infrastructure emergency. Prioritize affected public forums, high-traffic communities, and sites where moderator accounts may be weakly governed.
Technical view
CVE-2018-14724 is a stored XSS issue in the Ban List plugin 1.0 for MyBB. A forum user with moderator privileges can enter an XSS payload in the ban reason, which executes on bans.php. Sources do not provide CVSS, CWE, patch details, or a broader affected-version range.
Likely exposure
Exposure appears limited to MyBB deployments using Ban List plugin 1.0 and allowing moderator-level users to ban accounts. Evidence does not identify other versions or products.
Exploitation context
A public Exploit-DB reference exists, but the source bundle does not show confirmed active exploitation or CISA KEV listing. The attacker needs moderator privileges, so compromised or over-permissioned moderator accounts are the main concern.
Researcher notes
The record is sparse: no CVSS, CWE, patch, or precise CPE data is provided. Analysis is based on the CVE description and Exploit-DB reference only. Avoid assuming impact beyond stored XSS on bans.php through moderator-controlled ban reasons.
Mitigation direction
- Inventory MyBB sites for Ban List plugin 1.0.
- Check MyBB/plugin maintainer guidance for an official fix or replacement.
- Disable or remove the plugin if no trusted fix is available.
- Limit ban permissions to trusted moderator accounts only.
- Review moderator accounts for compromise or unnecessary access.
Validation and detection
- Confirm whether Ban List plugin 1.0 is installed.
- Review who has moderator privileges and ban capability.
- Inspect bans.php rendering behavior in a safe test environment.
- Search logs for unusual ban reasons or moderator activity.
- Verify any remediation against vendor or maintainer guidance.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2018-14724 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- 46347CVE reference · exploit, x_refsource_EXPLOIT-DB
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.