Skip to main content

Pin WP EUVDEUVD-2026-96490

| CVE-2026-62082 HIGH
Cross-site Scripting (XSS) (CWE-79)
2026-10-10 Patchstack GHSA-j5j4-8wgq-8wh6
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
    Deliver link to victim via phishing
  3. Exploit
    Victim clicks and payload reflects
  4. Execution
    Script executes in victim browser session
  5. Impact
    Hijack session or forge 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 the attacker to trick an authenticated or unauthenticated user of a site running the an-themes Pin WP theme (version 7.0 or earlier) into clicking a specially crafted URL that reflects an unsanitized input parameter back into the page (reflected XSS, CWE-79). The attacker needs no credentials (PR:N), but the attack is gated by mandatory victim interaction (UI:R) - without the victim following the malicious link, the payload does not execute - and impact is maximized when the victim is a privileged user such as a site administrator. The limiting factors are: the requirement for active social engineering to deliver the link, the reflected (non-persistent) nature meaning no stored payload on the server, and applicability only to sites that have the vulnerable Pin WP theme installed and active.

Impact

This is a moderate-risk, not top-priority, vulnerability. The CVSS 3.1 score of 7.1 (vector AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L) reflects a network-reachable, low-complexity, unauthenticated (PR:N) reflected XSS whose severity is inflated by the changed scope (S:C) typical of Patchstack's browser-context XSS scoring; the actual direct impact is only Low across confidentiality, integrity, and availability. The single most important mitigating signal is UI:R - exploitation requires a victim to be lured into clicking a crafted link, which makes this a targeted, social-engineering-dependent issue rather than a mass-exploitable server flaw. No EPSS score, no CISA KEV listing, and no public POC were provided in the input, consistent with 'no public exploit identified at time of analysis.' Because this is a reflected (not stored) XSS in a niche WordPress theme, there is no evidence of widespread or automated exploitation. Key missing data to note explicitly: EPSS probability is absent, so statistical likelihood cannot be quantified; exact affected sub-versions beyond '<= 7.0' and the specific vulnerable parameter/endpoint are not disclosed in the description. Overall: a legitimate issue worth patching on affected sites, but not an emergency relative to higher-impact or actively-exploited CVEs.

Exploit ScenarioDerived

An attacker crafts a malicious URL targeting the vulnerable Pin WP theme parameter and delivers it to a victim (e.g., a logged-in site administrator) via phishing email, chat, or a planted link. When the victim clicks it, the reflected payload executes JavaScript in their browser session in the site's context, enabling session/cookie theft, admin action forgery, or redirection. No public exploit code was identified at time of analysis, and success depends on the victim interacting with the attacker-supplied link (UI:R).

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

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

Alert me

AnalysisAIv1 – Oct 10, 2026

Reflected cross-site scripting in the an-themes Pin WP WordPress theme (versions 7.0 and earlier) allows an unauthenticated remote attacker to execute arbitrary script in a victim's browser by luring them to a specially crafted URL that reflects unsanitized input. Exploitation is gated by mandatory user interaction - no credentials are required, but the payload only fires if the victim clicks the attacker-supplied link - and the impact is worst when that victim is a logged-in site administrator, since the injected script inherits the site's origin (CVSS 7.1, S:C). No CISA KEV entry, no confirmed public exploit code, and no vendor-released patch were present in the available intelligence, so this rates as a moderate-risk, not top-priority, issue that nevertheless warrants prompt attention because of the volume of unauthenticated attackers who could attempt it.

RemediationAI

No vendor-released patch or fixed version is identified in the available intelligence, so the first step is to check the Patchstack vulnerability record at https://patchstack.com/database/wordpress/theme/pin-wp/vulnerability/wordpress-pin-wp-theme-7-0-reflected-cross-site-scripting-xss-vulnerability and the an-themes vendor site for an updated Pin WP release, then upgrade the theme as soon as one appears. If the theme is not essential, deactivating and removing it eliminates the exposure entirely, at the cost of losing whatever layout or functionality it provides; if it must stay, compensating controls are warranted in the interim. A web application firewall rule or reverse-proxy filter that blocks or sanitizes script-bearing query-string payloads is effective against reflected delivery, with the trade-off of tuning effort and potential false positives on legitimate parameters, and a Content-Security-Policy of script-src 'self' (ideally with nonces) will neuter injected inline script - though such a policy can break theme features and third-party embeds and needs testing before enforcement. Reduce the value of a successful hit by hardening session handling: advise administrators to open untrusted links in a separate browser that holds no authenticated session, and consider IP-restricting wp-admin and enabling two-factor authentication so a stolen session or nonce is harder to abuse. Finally, because exploitation leaves attacker-controlled payloads in URL query strings, review web-server and WAF logs for script-like parameters to detect attempted or successful targeting while a patch is pending.

Affected VersionsENISA

Pin WP n/a ≤7.0

Affected Packages

euvd pin_wp 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

CVE-2026-62082 is a classic CWE-79 'Improper Neutralization of Input During Web Page Generation' flaw in a WordPress theme. The affected component is the an-themes Pin WP theme, identified by CPE cpe:2.3:a:an-themes:pin_wp:*:*:*:*:*:*:*:*, which the vulnerability record scopes to version 7.0 and earlier; the Patchstack advisory classifies it specifically as a reflected XSS rather than a stored/persistent one. Reflected XSS means the theme echoes a request-supplied parameter back into the generated HTML without adequate output encoding or contextual escaping, so the payload lives only in the crafted URL and is never persisted server-side - this lowers the blast radius compared with stored XSS but keeps the attack trivial to deliver at scale. The CVSS vector CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L tells the story precisely: reachable over the network (AV:N) with no special conditions (AC:L) and no authentication (PR:N), but requiring the victim to interact (UI:R); the changed scope (S:C) indicates the injected script executes in the security context of the victim's browser and the hosting site's origin rather than staying confined to the vulnerable theme code, which is why even the 'low' confidentiality and integrity impacts can translate into session-token or nonce theft, forced administrative actions, redirects, or content injection on affected sites. Because the flaw sits in theme presentation code rather than in WordPress core, it is only exploitable on sites where the Pin WP theme is installed and active.

Know when Pin Wp 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 7.1 HIGH

Network-reachable reflected XSS needing no auth (PR:N) but victim click (UI:R); payload executes in browser context changing scope (S:C) with limited C/I/A impact.

3.1 AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
4.0 AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:N/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

Unauthenticated Cross Site Scripting (XSS) in Pin WP <= 7.0 versions.

Executive ViewAI

Why It Matters

The Pin WP theme for WordPress (versions 7.0 and earlier) contains a reflected cross-site scripting flaw that any unauthenticated attacker can attempt against any site running this theme, though the payload only fires if a victim clicks a crafted link. Risk concentrates on logged-in administrators, whose browser session could be leveraged to act with full site privileges, potentially enabling content tampering, credential or session theft, or complete site takeover. With no vendor patch available and a large pool of anonymous would-be attackers, leadership should treat this as a contained but time-sensitive exposure affecting every site using the affected theme.

Business Impact: Medium
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations: deploy WAF/virtual patching rules blocking reflected script payloads on the theme's URL parameters; remove, disable, or replace the Pin WP theme on internet-facing sites; enforce Content-Security-Policy and output encoding at the edge; shorten admin session lifetimes and require re-authentication for sensitive actions; and train administrators not to follow unsolicited links to their own site while logged in, since exploitation requires victim interaction.

Threat Intelligence Overview

EPSS Score
0.2%
Top 93% exploitable
Prevalence
Low
niche commercial WordPress theme, limited site deployment footprint
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.2%
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