LiveActive security incident?Get immediate response
CVE Record

CVE-2026-25304: WordPress Jaroti theme < 1.4.8 - Reflected Cross Site Scripting (XSS) vulnerability

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in skygroup Jaroti jaroti allows Reflected XSS.This issue affects Jaroti: from n/a through < 1.4.8.

HighCVSS 7.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-25304 affects the WordPress Jaroti theme before version 1.4.8. It is a reflected cross-site scripting issue, meaning a victim must interact with a crafted link or page for malicious script to run in their browser. The CVSS score is 7.1, rated high, but public sources provided do not show active exploitation.

Executive priority

Treat this as a high-priority web application hygiene issue for any public WordPress site using Jaroti. It is not confirmed as actively exploited in the provided sources, but XSS can support account abuse, data exposure, and reputational risk if users are targeted.

Technical view

The flaw is CWE-79 improper neutralization of input during web page generation in skygroup Jaroti. The CVSS vector is CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L, indicating network reachability, low complexity, no authentication, required user interaction, changed scope, and low confidentiality, integrity, and availability impact.

Likely exposure

Exposure is limited to WordPress sites using the Jaroti theme earlier than 1.4.8. The provided data does not identify affected endpoints, vulnerable parameters, or exploit prerequisites beyond reflected XSS and user interaction.

Exploitation context

No CISA KEV listing is indicated, and the provided sources do not claim active exploitation. Practical abuse would typically require convincing a user to open attacker-controlled content that triggers script execution in the context of the affected site.

Researcher notes

The CVE record lacks endpoint-level detail and CPEs. The affected version metadata in the bundle is sparse, so validation should rely on direct WordPress theme inventory and the Patchstack entry. Avoid assuming exploit availability or specific payload behavior from the provided evidence.

Mitigation direction

  • Inventory WordPress sites for the Jaroti theme and installed version.
  • Upgrade Jaroti to version 1.4.8 or later where available.
  • If upgrade is not possible, check vendor or Patchstack guidance for supported compensating controls.
  • Prioritize sites with authenticated users, customer portals, or administrative access exposure.

Validation and detection

  • Confirm whether the Jaroti theme is installed on each WordPress site.
  • Record the installed Jaroti version and compare it with 1.4.8.
  • Review web application security monitoring for suspicious XSS-like requests.
  • Verify the theme update completed successfully in staging and production.
Prepared
Confidence
high
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-2026-25304 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.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: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
7.1CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L2.83.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.1High
CVSS 3.1 vector shape for CVE-2026-25304Attack 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: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
skygroupJarotijaroti, 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.