PatchSiren cyber security CVE debrief
CVE-2018-25249 MyBB CVE debrief
The CVE record for CVE-2018-25249 was published on 2026-04-04T14:16:20.860Z and has not been modified since then. The NVD entry is currently Analyzed. This persistent cross-site scripting vulnerability in MyBB My Arcade Plugin 1.3 allows authenticated users to inject malicious scripts through arcade game score comments. The vulnerability has a CVSS score of 5.1 and a severity of MEDIUM. The affected product is MyBB My Arcade Plugin 1.3. The likely operational impact is that attackers can add crafted HTML and JavaScript payloads in the comment field that execute when other users view or edit the comment.
- Vendor
- MyBB
- Product
- MyBB My Arcade Plugin
- CVSS
- MEDIUM 5.1
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-04-04
- Original CVE updated
- 2026-07-21
- Advisory published
- 2026-04-04
- Advisory updated
- 2026-07-21
Who should care
Authenticated users of MyBB My Arcade Plugin 1.3 should be aware of this persistent cross-site scripting vulnerability, which allows attackers to inject malicious scripts through arcade game score comments. Operators, platform administrators, vulnerability management teams, and security teams should review the vulnerability and consider the potential impact on their systems.
Technical summary
CVE-2018-25249 is a persistent cross-site scripting vulnerability in MyBB My Arcade Plugin 1.3. Attackers can add crafted HTML and JavaScript payloads in the comment field that execute when other users view or edit the comment. The vulnerability has a CVSS score of 5.1 and a severity of MEDIUM. The affected product context is MyBB My Arcade Plugin 1.3. The defensive impact is that defenders should consider input validation and output encoding to prevent attackers from injecting malicious scripts.
Defensive priority
Medium priority due to the CVSS score and the potential for attackers to inject malicious scripts.
Recommended defensive actions
- Inventory and verify the version of MyBB My Arcade Plugin in use.
- Apply vendor remediation or patches if available.
- Implement compensating controls such as input validation and output encoding.
- Monitor for suspicious activity and exception tracking.
- Retest and verify the vulnerability has been remediated.
- Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance.
- Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed.
Evidence notes
The CVE record and NVD detail provide evidence of the vulnerability and its CVSS score. The source item URL and references provide additional information about the vulnerability and its impact. However, due to limited source detail, defenders should verify the affected scope and severity with the vendor and consider the potential for attackers to inject malicious scripts. The vulnerability has a CVSS score of 5.1 and a severity of MEDIUM. There are no known ransomware campaigns using this vulnerability. The CVE record was published on 2026-04-04T14:16:20.860Z and has not been modified since then.
Sources and references
Verified primary and authoritative sources
-
CVE-2018-25249 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2018-25249
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2018-25249 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2018-25249
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://www.exploit-db.com/exploits/44186
[email protected] - Exploit, VDB Entry
-
Mitigation or vendor reference
Unverified legacy reference
URL: https://www.vulncheck.com/advisories/mybb-my-arcade-plugin-persistent-xss-via-comment
[email protected] - Third Party Advisory
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.