LiveActive security incident?Get immediate response
CVE Record

CVE-2026-24948: WordPress Reflector plugin <= 1.2.2 - Reflected Cross Site Scripting (XSS) vulnerability

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in fox-themes Reflector reflector-plugins allows Reflected XSS.This issue affects Reflector: from n/a through <= 1.2.2.

HighCVSS 7.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-24948 is a reflected cross-site scripting issue in the WordPress Reflector plugin through version 1.2.2. An attacker could trick a user into opening a crafted link, causing script to run in that user’s browser. Business risk is highest for sites using this plugin with privileged administrators or logged-in users.

Executive priority

Prioritize review for public WordPress sites using Reflector, especially where administrators access the site frequently. Treat as high priority, but not an emergency based solely on current sources because active exploitation is not confirmed.

Technical view

The CVE identifies CWE-79 improper neutralization during web page generation in fox-themes Reflector, package reflector-plugins. CVSS 3.1 is 7.1 high: network exploitable, low complexity, no privileges required, user interaction required, scope changed, and low confidentiality, integrity, and availability impact.

Likely exposure

Exposure is limited to WordPress sites with the Reflector plugin installed at version 1.2.2 or earlier. The source bundle does not identify other affected products or deployment conditions.

Exploitation context

The CVSS vector requires user interaction, so exploitation likely depends on persuading a victim to visit a malicious link or page. The bundle marks KEV as false, and no cited source confirms active exploitation.

Researcher notes

Evidence is currently narrow: CVE and Patchstack identify reflected XSS through Reflector 1.2.2, but the provided sources do not name a fixed version, vulnerable parameter, proof of concept, or observed exploitation. Avoid assuming broader WordPress or theme impact.

Mitigation direction

  • Inventory WordPress sites for the Reflector plugin, package reflector-plugins.
  • Check Patchstack and vendor guidance for a fixed version or official mitigation.
  • Update if a patched version is available from trusted sources.
  • Disable or remove the plugin if it is not business-critical.
  • Use generic XSS protections such as WAF filtering where operationally appropriate.

Validation and detection

  • Confirm whether Reflector is installed on each WordPress site.
  • Record installed plugin versions and flag version 1.2.2 or earlier.
  • Review Patchstack and CVE entries for updated remediation information.
  • Check security logs for unusual requests targeting Reflector-related pages or parameters.
  • Validate remediation by confirming the vulnerable plugin is updated, disabled, or removed.
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-2026-24948 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-24948Attack 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
fox-themesReflectorreflector-plugins, 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.