Skip to main content

WPAdverts CVE-2026-97263

| EUVDEUVD-2026-96324 HIGH
Cross-site Scripting (XSS) (CWE-79)
2026-10-10 audit@patchstack.com GHSA-m8fh-8h6x-wrw7
7.1
CVSS 3.1 · Vendor: patchstack
View

Attack ChainAIDerived

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

  1. Access
    Submit crafted advert with script payload
  2. Delivery
    Payload stored unsanitized in WPAdverts
  3. Exploit
    Admin or visitor views affected page
  4. Execution
    Script executes in victim browser session
  5. Impact
    Hijack session or perform actions as victim

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 inject a script payload into a WPAdverts input field that is stored and later output without proper neutralization (stored XSS via the plugin's advert/content handling, versions through 2.3.4). Per the CVSS vector, triggering also requires victim user interaction (UI:R) - a privileged user or visitor must load the page containing the stored payload - which limits reliability and timing. The input vector asserts no privileges (PR:N), implying the injection point is reachable without authentication (consistent with a public advert-submission form), but the description does not name the specific field or confirm whether guest submission must be enabled; if WPAdverts requires an authenticated/contributor account to submit content, real-world privilege requirements are higher than PR:N suggests. The exact affected feature, parameter, and any non-default configuration dependency are not specified in the available data.

Impact

This is a moderate-severity (CVSS 7.1) stored cross-site scripting (CWE-79) issue in the WPAdverts WordPress plugin, reported by Patchstack. The supplied CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L) indicates a network-reachable, low-complexity flaw requiring victim interaction, with a scope change reflecting the cross-origin nature of XSS. Several enrichment signals that would normally drive prioritization are entirely ABSENT from the input: there is no EPSS probability, no CISA KEV listing, and no indication of public POC/exploit code - so exploitation likelihood cannot be quantified and should not be assumed high. The PR:N (unauthenticated) metric is notable and somewhat atypical for stored XSS, which usually requires the attacker to have some ability to persist content; it is plausible here only if WPAdverts' public advert-submission workflow accepts guest input, but this is NOT confirmed by the description and should be verified against the Patchstack advisory. Net assessment: a real but not emergency-tier issue - a classic 'high-CVSS, unproven-real-world-risk' stored XSS where impact is limited (C:L/I:L) and gated by user interaction, warranting routine patching rather than crisis response.

Exploit ScenarioDerived

An attacker submits a classified advert (or other user-supplied content) to a WPAdverts-powered site containing a malicious script payload that is stored and later rendered unsanitized. When a site administrator or another visitor views the affected page, the script executes in their browser session, enabling session/cookie theft or actions in the victim's context. No public exploit code was identified at the time of analysis, and successful attack depends on a victim viewing the poisoned page (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 10, 2026

Stored cross-site scripting in the WPAdverts WordPress plugin (all versions through 2.3.4) lets an attacker place crafted script content into advert data that is later rendered without proper neutralization, so the payload executes in the browser of any user who views the affected advert page. The reported base score is 7.1 (moderate); our assessed vector (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N) requires a low-privileged, authenticated submitter plus victim interaction, and the divergence from the published PR:N vector means the true privilege requirement hinges on whether WPAdverts is configured to allow unauthenticated advert submissions. No public exploit was identified at time of analysis, and no patch version is specified in the available intelligence, so the exposure is real but not confirmed actively abused.

RemediationAI

No vendor-released patch identified at time of analysis, and the provided data confirms only that versions through 2.3.4 are affected; administrators should check the Patchstack advisory (https://patchstack.com/database/wordpress/plugin/wpadverts/vulnerability/wordpress-wpadverts-plugin-2-3-4-cross-site-scripting-xss-vulnerability) for the fixed release and upgrade WPAdverts to the latest available version, verifying that the changelog documents the XSS fix before considering the site clean. If an immediate update is not possible, apply specific compensating controls: disable guest/unauthenticated advert submission and require an administrator to approve or moderate all advert content before it is published (trade-off: this suppresses automated marketplace-style posting and reduces ad volume), restrict advert-submission capability to trusted roles using a capability-management plugin (trade-off: legitimate contributor workflows may break), and configure a WAF with stored-XSS rules scoped to advert submission and rendering endpoints (trade-off: false positives on advert descriptions containing legitimate HTML, and WAF coverage cannot protect against payloads already stored). Because the vulnerability is stored, also scan and clean existing advert records for injected script tags after the fix, since patching the plugin does not remove payloads already written to the database; adding explicit output escaping to advert templates via a child theme or small must-use plugin helps until an official update lands, but can change how advert formatting is displayed.

Affected VersionsENISA

WPAdverts 0 ≤2.3.4

Affected Packages

euvd wpadverts 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, manifesting as the stored (persistent) XSS variant. WPAdverts is a WordPress classified-ads plugin (slug 'wpadverts', vendor Greg Winiarski) that accepts user-supplied advert fields - title, description, custom fields, images - and persists them in the WordPress database via the plugin's content handling routines. When those stored values are subsequently output on advert listing, single-advert, or management screens, insufficient escaping or sanitization allows HTML/JavaScript the attacker supplied at submission time to be interpreted by the browser as markup, so the script runs in the origin of the WordPress site. The scope-changed (S:C) component of both vectors reflects that the injected script is not confined to the plugin's own functionality and can reach site-wide resources - a major reason stored XSS in WordPress plugins is frequently chained into admin session theft or account takeover. No CPE strings were supplied in the intelligence feed, so artifact identification rests on the plugin slug 'wpadverts' pinned to versions through 2.3.4; the specific vulnerable parameter, field, and whether a non-default setting (such as guest/unauthenticated advert submission) is required are not stated in the available data.

Know when Wordpress Plugin 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 5.4 MEDIUM

Stored XSS typically requires some ability to persist content, so PR:L rather than PR:N; victim must view the page (UI:R), scope changes to the victim's context (S:C), and XSS has no genuine availability impact (A:N).

3.1 AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
4.0 AV:N/AC:L/AT:N/PR:L/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 Greg Winiarski WPAdverts wpadverts allows Stored XSS.This issue affects WPAdverts: from n/a through 2.3.4.

Executive ViewAI

Why It Matters

WPAdverts, a WordPress plugin for classified ads, contains a stored cross-site scripting vulnerability (CVE-2026-97263) in all versions through 2.3.4. A malicious user with basic access could inject scripts that run in the browsers of visitors to affected ad pages, potentially leading to session hijacking or data theft. With no vendor patch yet available, leadership should prioritize interim mitigations to protect users and the organization's web presence.

Business Impact: Medium
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations include: disable the WPAdverts plugin; restrict advert submission to trusted authenticated users; deploy a web application firewall (WAF) to filter malicious script content; enforce strict input sanitization and output encoding on all advert data; monitor logs for exploitation attempts.

Threat Intelligence Overview

EPSS Score
0.1%
Top 97% exploitable
Prevalence
Low
niche WordPress classifieds plugin, modest install base
Social Media
1
Sightings
Data Quality
7 sources
Confidence: High

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.

CVE-2023-6553 CRITICAL POC
9.8 Dec 15

The Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1

CVE-2024-5084 CRITICAL POC
9.8 May 23

The Hash Form - Drag & Drop Form Builder plugin for WordPress is vulnerable to arbitrary file uploads due to missing fil

CVE-2024-44000 CRITICAL POC
9.8 Oct 20

Authentication bypass in the LiteSpeed Cache WordPress plugin (versions prior to 6.5.0.1) allows unauthenticated remote

CVE-2020-36847 CRITICAL POC
9.8 Jul 12

The Simple File List plugin for WordPress through version 4.2.2 contains an unauthenticated remote code execution vulner

CVE-2025-27007 CRITICAL POC
9.8 May 01

The SureTriggers WordPress plugin through version 1.0.82 contains a privilege escalation vulnerability that allows unaut

CVE-2016-1209 CRITICAL POC
9.8 May 14

The Ninja Forms plugin before 2.9.42.1 for WordPress allows remote attackers to conduct PHP object injection attacks via

CVE-2024-4443 CRITICAL POC
9.8 May 22

The Business Directory Plugin - Easy Listing Directories for WordPress plugin for WordPress is vulnerable to time-based

CVE-2024-1698 CRITICAL POC
9.8 Feb 27

SQL injection in the NotificationX WordPress plugin (versions up to and including 2.8.2) allows unauthenticated remote a

CVE-2023-6875 CRITICAL POC
9.8 Jan 11

The POST SMTP Mailer - Email log, Delivery Failure Notifications and Best Mail SMTP for WordPress plugin for WordPress i

CVE-2024-1512 CRITICAL POC
9.8 Feb 17

The MasterStudy LMS WordPress Plugin - for Online Courses and Education plugin for WordPress is vulnerable to union base

CVE-2024-4295 CRITICAL POC
9.8 Jun 05

The Email Subscribers by Icegram Express plugin for WordPress is vulnerable to SQL Injection via the ‘hash’ parameter in

CVE-2024-50498 CRITICAL POC
10.0 Oct 28

Remote code execution in the WP Query Console WordPress plugin (versions up to and including 1.0) by Ajit Bohra allows u

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