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

CVE-2026-7660

MEDIUM · 6.1 CVSS v3.1 Published 2026-05-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 Easy Updates Manager plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the 'paged' parameter in versions up to, and including, 9.0.20 This is due to insufficient input sanitization and output escaping in the pagination() function. This makes it possible for attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page granted they can trick an administrator into performing an action such as clicking on a link.

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 · high confidence

The Easy Updates Manager WordPress plugin versions up to 9.0.20 contain a reflected Cross-Site Scripting vulnerability in the pagination() function. The 'paged' parameter is not properly sanitized on input or escaped on output, allowing attackers to inject arbitrary JavaScript via a malicious URL that tricks administrators into clicking it.

MitigationUpgrade Easy Updates Manager to version 9.0.21 or later. Until then, administrators should avoid clicking untrusted links pointing to the plugin's admin pages.

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
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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. Verify Easy Updates Manager plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Easy Updates Manager' in the list
    Affected if Plugin is not found in the installed plugins list
  2. Check the installed version of Easy Updates Manager
    On the Plugins page, find Easy Updates Manager and note the version number displayed beneath the plugin name; or check the plugin's main PHP file header for 'Version:' tag
    Affected if Version number is 9.0.20 or earlier
  3. Confirm the plugin is active
    On the Plugins page, verify that Easy Updates Manager shows as 'Active' under the plugin status
    Affected if Plugin is active and running
  4. Test for the vulnerable paged parameter
    Navigate to any Easy Updates Manager admin page (e.g., Dashboard > Updates), then append '?paged=<script>alert(1)</script>' to the URL and check if the script executes or appears unescaped in the page
    Affected if The paged parameter value is reflected literally in the HTML without encoding or the script executes

If Easy Updates Manager version 9.0.20 or earlier is active and the paged parameter is reflected without sanitization, the environment is affected by this XSS vulnerability.

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

Upgrade Easy Updates Manager to version 9.0.21 or later. Until then, administrators should avoid clicking untrusted links pointing to the plugin's admin pages.

Recommended fix Moderate confidence

Upgrade Easy Updates Manager to version 9.0.21 or later (the first version after 9.0.20)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate Easy Updates Manager in the plugin list
  4. Check if the current version is 9.0.20 or earlier
  5. If vulnerable, click 'Update Now' to install the latest version
  6. Alternatively, download the latest version from wordpress.org/plugins/stops-core-theme-and-plugin-updates/ and upload via Plugins > Add New > Upload Plugin
  7. After update, verify the version number reflects the patched release

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-7660 — 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-2026-7660 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