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

CVE-2026-13245

MEDIUM · 6.1 CVSS v3.1 Published 2026-06-27
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 8 weeks old

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 MaxButtons – Create buttons plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the 'view' parameter in all versions up to, and including, 9.8.5 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user 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 MaxButtons WordPress plugin versions up to 9.8.5 contain a reflected XSS vulnerability in the 'view' parameter due to insufficient input sanitization and output escaping. Unauthenticated attackers can craft malicious URLs that, when clicked by a victim, execute arbitrary JavaScript in the user's browser.

MitigationUpdate the MaxButtons plugin to the latest patched version once available. As a temporary measure, implement a WAF rule to block requests with suspicious patterns in the 'view' parameter and educate users about not clicking untrusted links.

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. Confirm MaxButtons plugin is installed
    Check the WordPress plugins directory (wp-content/plugins/) or view the installed plugins list in the WordPress admin under Plugins > Installed Plugins. Look for 'MaxButtons' or 'maxbuttons' in the plugin list.
    Affected if MaxButtons plugin appears in the installed plugins list
  2. Identify the installed MaxButtons version
    In WordPress admin, go to Plugins > Installed Plugins and find MaxButtons. The version number is displayed below the plugin name. Alternatively, check the plugin's main PHP file header for 'Version:' comment or inspect the plugin metadata via WP-CLI: wp plugin list --name=maxbuttons.
    Affected if The displayed version number is 9.8.5 or lower
  3. Determine if the site is accessible to unauthenticated users
    Verify that the WordPress admin area or the MaxButtons plugin pages are accessible without authentication. Try accessing a typical MaxButtons admin URL (such as /wp-admin/admin.php?page=maxbuttons-pro or similar) without logging in.
    Affected if The MaxButtons admin interface or its endpoints are accessible to unauthenticated users (not protected by login requirement)
  4. Inspect the 'view' parameter handling
    Access a MaxButtons admin page URL and observe the 'view' parameter in the query string. Check the plugin's PHP source code (typically in the main plugin file or admin class) for how the 'view' parameter is handled - look for whether it uses sanitize_text_field, esc_html, or similar sanitization functions before output.
    Affected if The plugin code does not sanitize or escape the 'view' parameter before using it in HTML output, or the parameter is reflected back in the response without encoding

A user is affected if MaxButtons plugin version 9.8.5 or lower is installed, the plugin is accessible to unauthenticated users, and the 'view' parameter is not properly sanitized before output.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the MaxButtons plugin to the latest patched version once available. As a temporary measure, implement a WAF rule to block requests with suspicious patterns in the 'view' parameter and educate users about not clicking untrusted links.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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