What is the CVSS score of CVE-2025-5085?

CVE-2025-5085 has a CVSS 3.1 base score of 5.5 (Medium). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:L/A:N. EPSS exploitation probability: 0.0%.

WP Nano AD CVE-2025-5085

EUVD-2025-210029 MEDIUM

Cross-site Scripting (XSS) (CWE-79)

2026-06-02 Wordfence

GHSA-62p6-3xjc-94cc

XSS WordPress

5.5

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

5.5 MEDIUM

AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:L/A:N

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:L/A:N

Attack Vector

Network

Attack Complexity

Low

Privileges Required

High

User Interaction

None

Scope

Changed

Confidentiality

Low

Integrity

Low

Availability

None

Lifecycle Timeline

Analysis Generated

Jun 02, 2026 - 08:48 vuln.today

CVE Published

Jun 02, 2026 - 07:48 nvd

MEDIUM 5.5

DescriptionCVE.org

The WP Nano AD plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘blogrole_link’ parameter in all versions up to, and including, 1.31 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with administrator-level access, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This only affects multi-site installations and installations where unfiltered_html has been disabled.

AnalysisAI

Stored Cross-Site Scripting in the WP Nano AD WordPress plugin (all versions through 1.31) allows authenticated administrators to inject persistent malicious scripts via the 'blogrole_link' parameter in add_links.php, with execution occurring in any victim's browser upon visiting the compromised page. Exploitation is restricted to WordPress multi-site networks or single-site installations where the unfiltered_html capability has been explicitly disabled - notably a configuration common in security-hardened deployments. No public exploit identified at time of analysis, though a public security writeup by BFS-Lab has been published on GitHub, increasing the likelihood of weaponized attempts against qualifying environments.

Technical ContextAI

WP Nano AD is a WordPress advertising management plugin by the vendor ariyes (CPE: cpe:2.3:a:ariyes:wp_nano_ad:*:*:*:*:*:*:*:*). The root cause is CWE-79 (Improper Neutralization of Input During Web Page Generation), specifically a stored variant: the 'blogrole_link' parameter accepted by add_links.php is written to persistent storage and later rendered in page output without adequate sanitization or output escaping. WordPress's unfiltered_html capability normally permits administrators to submit raw HTML and script - when this capability is revoked (a standard hardening measure, and the default on multi-site networks for non-super-admins), the plugin fails to apply compensating escaping, creating a sink for injected payloads. The CVSS Changed Scope (S:C) correctly reflects that the XSS payload crosses the security boundary from the injecting administrator's session into arbitrary authenticated or unauthenticated visitor sessions.

RemediationAI

No specific patched release version is confirmed in the available intelligence data - the CPE wildcard and absence of a fixed-version reference in advisory metadata means a remediated release has not been independently verified. Administrators should check the WordPress plugin repository at https://cor.wordpress.org/plugins/wp-nano-ad/ for any release beyond 1.31 and consult the Wordfence advisory for updated patch confirmation. Until a patched version is confirmed, the most effective compensating control is to deactivate and remove the WP Nano AD plugin entirely, eliminating the attack surface with no service-continuity trade-off beyond loss of plugin functionality. If removal is not feasible, restrict WordPress administrator role assignment strictly to fully trusted internal personnel, reducing the likelihood that an attacker holds qualifying credentials. In multi-site environments, audit which users hold site-admin privileges, as those accounts provide sufficient access to exploit this flaw. Note that re-enabling unfiltered_html for administrators would technically remove the triggering condition for this specific vulnerability, but doing so weakens the broader security posture and is not recommended as a primary mitigation.