Skip to main content

SpabRice Pond EUVDEUVD-2026-95787

| CVE-2026-94066 HIGH
Cross-site Scripting (XSS) (CWE-79)
2026-10-09 Patchstack GHSA-vmrf-m5x3-48m3
7.1
CVSS 3.1 · Vendor: Patchstack
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Craft malicious URL with XSS payload
  2. Delivery
    Phish victim into clicking link
  3. Exploit
    Theme reflects payload unsanitized
  4. Execution
    Script executes in victim browser
  5. Impact
    Steal session or perform admin actions

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Output encoding, context-aware escaping
MITRE ATT&CK

2 techniques across 2 tactics: Initial Access, Execution

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires an attacker to deliver a specially crafted URL containing a script payload to a victim and have that victim open it in a browser (UI:R), causing the Pond theme to reflect the unsanitized input back into the generated page. No authentication is required of the attacker (PR:N), but the attack is LIMITED by mandatory user interaction (victim must click the malicious link) and by the reflected (non-persistent) nature of the flaw, which means it cannot be triggered without active social engineering and does not persist on the server. Highest impact is realized when the lured victim is an authenticated administrator, as the script then runs in that privileged browser context. Affected scope: any site running the SpabRice Pond theme up to and including version 2.6.1.

Impact

This is a reflected cross-site scripting (CWE-79) flaw in the SpabRice 'Pond' WordPress theme. The provided CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L, base 7.1 High) indicates a network-reachable, low-complexity, unauthenticated attack that nonetheless REQUIRES user interaction (UI:R) and carries only Low confidentiality, integrity, and availability impact with a changed scope (S:C, reflecting payload execution in the victim's browser outside the vulnerable component). No EPSS score, KEV listing, or public POC was supplied with this intelligence, so exploitation likelihood cannot be quantified from the data and there is no public exploit identified at time of analysis. Realistically this is a classic reflected-XSS issue: the 7.1 base score overstates practical priority because successful attacks hinge on social-engineering a victim into clicking a crafted link, and reflected XSS is not self-propagating. Treat it as a standard-priority patch item (session/credential theft, admin-targeted phishing) rather than an urgent mass-exploitation threat, especially given the niche deployment footprint of this theme. Note: the absence of EPSS/KEV/POC is a data gap, not evidence of safety.

Exploit ScenarioDerived

An attacker crafts a URL for a Pond-powered WordPress site containing a malicious script in a parameter that the theme reflects unsanitized into the page. The attacker sends this link to a site administrator or logged-in user via phishing; when the victim clicks it, the script executes in their browser session, enabling session-cookie theft or actions in their authenticated context. No public exploit code was provided in this intelligence, and the attack depends on the victim's interaction (UI:R).

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 0.1% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 09, 2026

Reflected cross-site scripting in the SpabRice Pond WordPress theme (all versions through 2.6.1) lets a remote, unauthenticated attacker craft a URL containing a script payload that the theme reflects unsanitized into the generated page; the victim must be convinced to open that link (mandatory user interaction), so exploitation cannot occur without social engineering and nothing persists server-side. Impact per the assessed vector is low confidentiality and integrity loss with scope change, with the worst case being a lured authenticated administrator whose browser executes the script in a privileged session; no public exploit and no confirmed active exploitation were identified at time of analysis. Sites running this theme should treat the reflected payload as a phishing/CSRF-assist vector rather than a self-propagating compromise.

RemediationAI

No vendor-released patch for the SpabRice Pond theme was identified at time of analysis, and the only reference supplied is the Patchstack advisory (https://patchstack.com/database/wordpress/theme/pond/vulnerability/wordpress-pond-theme-2-6-1-reflected-cross-site-scripting-xss-vulnerability?_s_id=cve), so remediation starts by monitoring that advisory and the theme vendor for a fixed release and upgrading immediately once a version above 2.6.1 is published. Until then, the highest-value compensating control is to deactivate and, if it is not required, uninstall the Pond theme entirely, which removes the vulnerable templates from the render path at zero functional cost if another theme is already in use; the trade-off is loss of the theme's styling and any customization work. If the theme must stay active, deploy a web application firewall or reverse-proxy rule that inspects query strings and blocks requests containing HTML/script metacharacters or common XSS payload patterns on site URLs, accepting the trade-off of occasional false positives on legitimate content and the fact that WAF evasion is common for reflected XSS. Because the vulnerability is reflected and requires a victim to click a crafted link, additional user-side controls help: ensure WordPress administrator and editor sessions use HttpOnly and Secure cookie flags, restrict admin-area access by IP or VPN where feasible, and train privileged users not to follow unsolicited links to the site. If custom template edits are possible, review theme files that echo request parameters and wrap those values in esc_html(), esc_attr(), or esc_url() output encoding; note that WordPress core updates do not patch third-party theme code, so this must be applied to the theme itself or via a maintained child theme, and unencoded theme modifications can be overwritten by future theme updates.

Affected VersionsENISA

Pond 0 ≤2.6.1

Affected Packages

euvd pond no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The root cause is CWE-79, improper neutralization of input during web page generation, in a PHP-based WordPress theme, the SpabRice 'Pond' theme, tracked by the CPE cpe:2.3:a:spabrice:pond:*:*:*:*:*:*:*:* with the wildcard version range matching all releases up to and including 2.6.1. WordPress themes frequently build URLs from query parameters and echo them directly into generated HTML (search results, error notices, navigation links) without context-appropriate output encoding such as esc_html() or esc_attr(); when an attacker-supplied parameter is returned to the browser verbatim, the browser parses it as markup or script in the origin of the affected WordPress site. Because the flaw is reflected rather than stored, the payload lives only in the crafted request and is not written to the database. The assessed CVSS vector CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N confirms network reachability, no attacker authentication (PR:N) and a scope change (S:C), meaning the injected script executes in the context of the hosting site and can act on that origin (for example reading non-HttpOnly cookies, issuing same-site requests, or injecting content) once the victim interacts with the link; the mandatory UI:R condition and the absence of persistence are what keep the practical severity below full compromise.

Know when Pond gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (Patchstack) PRIMARY 7.1 HIGH
AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
vuln.today AI 6.1 MEDIUM

Network-reachable unauthenticated reflected XSS (AV:N/AC:L/PR:N) requires victim click (UI:R) and runs in the browser (S:C) with low C/I; no availability impact typical for reflected XSS, so A:N.

3.1 AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
4.0 AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N

Primary rating from Vendor (Patchstack).

CVSS VectorVendor: Patchstack

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

DescriptionCVE.org

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in SpabRice Pond pond allows Reflected XSS.This issue affects Pond: from n/a through 2.6.1.

Executive ViewAI

Why It Matters

All versions through 2.6.1 of the SpabRice Pond WordPress theme contain a reflected cross-site scripting flaw that attackers can trigger by luring a victim - potentially a logged-in administrator - into opening a crafted link. Because the payload is reflected rather than stored, the practical risk to the organization is credential and session theft or unauthorized privileged actions executed in a hijacked admin browser, not mass site compromise. Leadership should care because no vendor fix currently exists, meaning any externally facing site running this theme remains exposed until mitigating controls are deployed.

Business Impact: Medium
Compensating Controls

No vendor-released patch identified at time of analysis; interim mitigations are virtual patching via WAF or reverse-proxy rules targeting reflected script payloads, strict Content-Security-Policy headers blocking inline scripts, temporary deactivation or replacement of the SpabRice Pond theme, shortened administrator session lifetimes, and phishing-awareness guidance to privileged users. No public exploit identified at time of analysis.

Threat Intelligence Overview

EPSS Score
0.1%
Top 97% exploitable
Prevalence
Low
niche WordPress theme, limited real-world installation base
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.1%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact
Medium
Technical Impact
Partial

Priority Score

36
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +36
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy