LiveActive security incident?Get immediate response
CVE Record

CVE-2021-25984: FactorJS - Stored Cross-Site Scripting (XSS) in Post Reply Functionality

In Factor (App Framework & Headless CMS) forum plugin, versions v1.3.3 to v1.8.30, are vulnerable to stored Cross-Site Scripting (XSS) at the “post reply” section. An unauthenticated attacker can execute malicious JavaScript code and steal the session cookies.

MediumCVSS 6.1Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

FactorJS Factor forum pages may store unsafe reply content, letting an unauthenticated attacker run JavaScript in another user's browser when they view the reply. Business impact is account compromise risk, especially if administrator or authenticated-user sessions are exposed.

Executive priority

Treat as a moderate web application risk. Prioritize internet-facing community or support forums, especially where administrators browse user-submitted replies while logged in.

Technical view

CVE-2021-25984 is stored XSS in the Factor forum plugin post reply functionality, reported for versions v1.3.3 through v1.8.30. CVSS 3.1 is 6.1: network exploitable, low complexity, no privileges, user interaction required, changed scope, low confidentiality and integrity impact.

Likely exposure

Exposure is most likely where FactorJS Factor uses the forum plugin with public or unauthenticated reply posting enabled, particularly on internet-facing sites running v1.3.3 through v1.8.30.

Exploitation context

The source bundle says an unauthenticated attacker can execute malicious JavaScript and steal session cookies. It does not show KEV listing or other evidence of active exploitation in the wild.

Researcher notes

Evidence identifies the vulnerable component and affected range, but the bundle does not name a fix version, patch commit, or active exploitation. Validation should stay non-destructive and focus on version exposure, forum configuration, and safe rendering behavior.

Mitigation direction

  • Check FactorJS vendor guidance for fixed or unaffected versions.
  • Upgrade away from affected Factor forum plugin versions when vendor guidance identifies a fix.
  • Disable or restrict unauthenticated forum replies until remediation is complete.
  • Ensure reply content is sanitized and safely rendered before storage and display.
  • Use HttpOnly, Secure, and SameSite cookie settings to reduce session theft impact.

Validation and detection

  • Inventory FactorJS Factor deployments and forum plugin usage.
  • Confirm whether deployed versions fall between v1.3.3 and v1.8.30.
  • Verify public reply posting is disabled, authenticated, or protected by server-side sanitization.
  • Review stored forum replies for suspicious script-like content.
  • Confirm session cookies use defensive attributes where supported.
Prepared
Confidence
medium
Sources
4

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-2021-25984 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
Medium
CVSS
6.1 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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
3Source 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
6.1CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N2.82.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.1Medium
CVSS 3.1 vector shape for CVE-2021-25984Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
FactorJSFactor1.3.3, unspecifiedListed
Weakness

CWE details

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