dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2025-5085

MEDIUM · 5.5 CVSS v3.1 Published 2026-06-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
61/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

The WP Nano AD WordPress plugin is vulnerable to Stored XSS via the 'blogrole_link' parameter in versions up to 1.31. Authenticated administrators can inject malicious scripts due to missing input sanitization and output escaping. Exploitation is limited to multi-site installations or sites where unfiltered_html is disabled.

MitigationUpdate the plugin to the latest version when available. Until then, restrict administrator access, disable the plugin if unnecessary, and ensure unfiltered_html is properly configured on single-site installations.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
High
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm WP Nano AD plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'WP Nano AD', or check the plugin files in /wp-content/plugins/ for a nano-ad folder containing the main plugin file
    Affected if The plugin is not installed on the WordPress site
  2. Identify the installed plugin version
    Open the main plugin file (usually nano-ad.php or similar) in /wp-content/plugins/nano-ad/ and look for the version defined in the plugin header comment (e.g., 'Version: 1.31')
    Affected if The version is 1.31 or lower (any version up to and including 1.31)
  3. Determine WordPress multi-site status
    Check WordPress configuration: look for 'MULTISITE' defined as true in wp-config.php, or go to Network Admin > Dashboard to see if it shows a network admin interface
    Affected if WordPress is configured as multi-site (is_multisite() returns true)
  4. Check unfiltered_html capability status
    In single-site installations, check if the administrator role still has the unfiltered_html capability by using a plugin like User Role Editor or running a PHP check: $role = get_role('administrator'); echo $role->has_cap('unfiltered_html');
    Affected if On single-site, the administrator role does NOT have unfiltered_html capability (has_cap returns false)
  5. Verify blogrole_link parameter is in use
    Check plugin settings pages for any field labeled 'blogrole_link' or similar, or inspect the plugin code for $_POST['blogrole_link'] or similar parameter handling
    Affected if The blogrole_link parameter is present and configurable in the plugin settings

The site is affected if WP Nano AD plugin version 1.31 or lower is installed AND (WordPress is multi-site OR unfiltered_html capability is disabled for administrators) AND the blogrole_link parameter is configurable.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to the latest version when available. Until then, restrict administrator access, disable the plugin if unnecessary, and ensure unfiltered_html is properly configured on single-site installations.

Recommended fix Moderate confidence

WP Nano AD version 1.32 or latest available version

  1. 1. Navigate to the WordPress admin dashboard
  2. 2. Go to Plugins > Installed Plugins
  3. 3. Locate the WP Nano AD plugin
  4. 4. Check if an update is available and update to the latest version
  5. 5. If no update is available through the WordPress admin, download the latest version from the official WordPress plugin repository
  6. 6. Deactivate the current plugin version
  7. 7. Delete the current plugin files
  8. 8. Upload and install the updated version

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-5085 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-5085 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data