LiveActive security incident?Get immediate response
CVE Record

CVE-2018-25250: MyBB Last User's Threads in Profile Plugin 1.2 Persistent XSS

MyBB Last User's Threads in Profile Plugin 1.2 contains a persistent cross-site scripting vulnerability that allows attackers to inject malicious scripts by crafting thread subjects with script tags. Attackers can create threads with script payloads in the subject field that execute when users visit the attacker's profile page.

HighCVSS 7.2Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2018-25250 affects version 1.2 of the MyBB “Last User's Threads in Profile” plugin. An attacker can create a forum thread with a malicious subject that is stored and later runs in visitors’ browsers when they view the attacker’s profile. This can expose user sessions or alter page content in the context of the forum.

Executive priority

Prioritize internet-facing forums that allow public registration or posting. The business risk is account compromise, user trust damage, and malicious content execution in visitors’ browsers. Treat as high priority where the affected plugin is present.

Technical view

The issue is persistent cross-site scripting, CWE-79. The vulnerable plugin appears to render thread subjects on profile pages without safe output handling. The CVSS 3.1 score is 7.2 with network attack vector, low complexity, no privileges required, and changed scope. Sources identify version 1.2 as affected.

Likely exposure

Exposure is limited to MyBB sites using the Last User's Threads in Profile plugin version 1.2. Organizations not running MyBB or this plugin are not affected based on the provided sources.

Exploitation context

A public ExploitDB reference exists, but the source bundle does not show CISA KEV listing or confirmed active exploitation. Exploitation requires creating a thread subject that is later displayed to users visiting the attacker’s profile page.

Researcher notes

The public record identifies the vulnerable component and behavior, but the supplied sources do not name a fixed release. Avoid assuming core MyBB is affected; the issue is tied to the third-party profile plugin version 1.2.

Mitigation direction

  • Inventory MyBB installations for this specific plugin and version 1.2.
  • Check the MyBB mod page and vendor guidance for fixed versions or instructions.
  • If no fix is available, consider disabling or removing the plugin after business review.
  • Restrict untrusted forum posting where feasible until remediation is complete.

Validation and detection

  • Confirm whether the plugin is installed on each MyBB forum.
  • Verify the installed plugin version against affected version 1.2.
  • Review profile pages that list user threads for unsafe rendering of thread subjects.
  • Use safe, non-executable test strings in a controlled environment only.
Prepared
Confidence
medium
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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.

cwe · medium confidence lookup

CWE-79: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2018-25250 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.2 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N

Official CVE source material

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.

1CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.2CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N3.92.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.2High
CVSS 3.1 vector shape for CVE-2018-25250Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
MyBBMyBB Last User's Threads in Profile Plugin1.2Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-79 · source CWE mapping

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.