LiveActive security incident?Get immediate response
CVE Record

CVE-2025-31419: WordPress Churel plugin <= 1.0.8 - Cross Site Scripting (XSS) vulnerability

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Themeix Churel allows DOM-Based XSS.This issue affects Churel: from n/a through 1.0.8.

MediumCVSS 6.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2025-31419 is a medium-severity cross-site scripting issue in Themeix Churel for WordPress through version 1.0.8. A successful attack could run unwanted script in a user's browser, with limited confidentiality, integrity, and availability impact. The public bundle does not identify a fixed version.

Executive priority

Prioritize remediation for public WordPress sites using Churel, especially where many users or customers authenticate. This is not presented as actively exploited, but XSS in a public site can create reputational and account-risk exposure.

Technical view

The issue is CWE-79 DOM-based XSS caused by improper input neutralization during page generation. CVSS 3.1 is 6.5: network reachable, low complexity, low privileges required, user interaction required, changed scope, and low C/I/A impact.

Likely exposure

Exposure is most likely on WordPress sites using Themeix Churel version 1.0.8 or earlier. The bundle provides no CPEs and does not clarify whether all installations or specific configurations are affected, so asset inventory is required.

Exploitation context

The source bundle does not show CISA KEV listing or cited evidence of active exploitation. It also does not provide exploit details, public proof of concept status, vulnerable parameters, or telemetry. Treat exploitation status as unconfirmed.

Researcher notes

The public bundle is sparse. It identifies DOM-based XSS through 1.0.8, CVSS 6.5, CWE-79, and Patchstack as the VDB source, but omits fixed-version, root-cause, parameter, and exploit-status details. Validate only in authorized environments.

Mitigation direction

  • Inventory WordPress sites for Themeix Churel and record installed versions.
  • Check Themeix and Patchstack guidance for a fixed release or vendor mitigation.
  • Update Churel if a vendor-supported fixed version is available.
  • Disable or replace Churel where affected and no fix is available.
  • Limit WordPress administrative access to trusted users only.
  • Monitor affected sites for unexpected script changes or suspicious content edits.

Validation and detection

  • Confirm whether Churel is installed on each WordPress property.
  • Compare installed versions against affected range through 1.0.8.
  • Review vendor and Patchstack records for current remediation status.
  • Check whether vulnerable pages are reachable by authenticated low-privilege users.
  • Review recent site changes for unexpected client-side script injection.
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-31419 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-31419Attack 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
ThemeixChurelchurel, n/aunaffected
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.