LiveActive security incident?Get immediate response
CVE Record

CVE-2025-31532: WordPress AtomChat plugin <= 1.1.8 - Cross Site Scripting (XSS) vulnerability

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Team AtomChat AtomChat atomchat allows Stored XSS.This issue affects AtomChat: from n/a through <= 1.1.8.

MediumCVSS 6.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2025-31532 is a stored cross-site scripting issue in the WordPress AtomChat plugin. A lower-privileged user could cause malicious script content to be stored and later run in another user's browser. Sources rate it medium severity, but impact depends on whether the plugin is installed and who can submit AtomChat content.

Executive priority

Treat this as a targeted WordPress plugin exposure, not a broad emergency. Prioritize internet-facing or customer-facing sites using AtomChat, especially where untrusted users can create chat or profile content.

Technical view

The CVE describes CWE-79 improper neutralization during web page generation in Team AtomChat AtomChat for WordPress, affecting versions through <= 1.1.8. CVSS 3.1 is 6.5 with network access, low complexity, low privileges required, user interaction required, changed scope, and low C/I/A impact.

Likely exposure

Exposure is likely limited to WordPress sites running the AtomChat plugin at affected versions. The bundle does not prove all WordPress sites are affected, and the affected-version metadata is partially inconsistent, so confirm installed plugin versions directly.

Exploitation context

The provided sources do not indicate active exploitation, and the CVE is not listed as KEV. The CVSS vector indicates exploitation requires a logged-in or otherwise low-privileged actor and user interaction, consistent with stored XSS triggered when another user views affected generated content.

Researcher notes

Evidence supports stored XSS, CWE-79, medium CVSS 6.5, and no KEV listing. The source bundle contains a discrepancy between <= 1.1.8 in the CVE description and a Patchstack URL naming 1.1.6, so verify vendor records before final scoping.

Mitigation direction

  • Inventory WordPress sites for the AtomChat plugin.
  • Confirm whether installed AtomChat versions are <= 1.1.8.
  • Check Team AtomChat or Patchstack guidance for a fixed version.
  • Update, disable, or remove AtomChat where vendor guidance supports it.
  • Restrict plugin access to trusted users until remediation is confirmed.

Validation and detection

  • Review WordPress plugin inventory and recorded AtomChat versions.
  • Check CVE and Patchstack records for updated affected-version details.
  • Review AtomChat-related content for unexpected embedded script-like data.
  • Verify remediation by confirming the installed version is outside the affected range.
  • Document any sites where AtomChat remains enabled pending vendor guidance.
Prepared
Confidence
medium
Sources
3

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-2025-31532 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.5 (3.1)
Known Exploited
No
Published

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

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
2Source 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.5CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L2.33.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.5Medium
CVSS 3.1 vector shape for CVE-2025-31532Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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
Team AtomChatAtomChatatomchat, 0unaffected
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.