dbcve.org
MaxbuttonsWordPress extension · Maxbuttons Project

CVE-2017-2169

MEDIUM · 6.1 CVSS v3.0 Published 2017-05-22
Fix available
A fix is available. Upgrade to after 6.18 or later.
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
Cross-site scripting vulnerability in MaxButtons prior to version 6.19 and MaxButtons Pro prior to version 6.19 allows remote attackers to inject arbitrary web script or HTML via unspecified vectors.

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

Cross-site scripting (XSS) vulnerability in MaxButtons WordPress plugin versions prior to 6.19 allows remote attackers to inject arbitrary JavaScript or HTML through unspecified vectors, potentially allowing session hijacking or malicious actions in authenticated users' browsers.

MitigationUpdate MaxButtons (both free and Pro versions) to version 6.19 or later to remediate the vulnerability.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
MaxbuttonsWordPress extension
Affected:<= 6.18

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.0/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 MaxButtons plugin is installed
    Check your WordPress installation by navigating to wp-content/plugins/ directory or via WordPress admin under Plugins > Installed Plugins. Look for MaxButtons or MaxButtons Pro.
    Affected if MaxButtons plugin is present in the WordPress installation
  2. Check installed MaxButtons version
    In WordPress admin, go to Plugins > Installed Plugins and locate MaxButtons. The version number is displayed below the plugin name. Alternatively, open the main plugin file (e.g., maxbuttons.php) in wp-content/plugins/maxbuttons/ and find the 'Version:' header comment.
    Affected if Version number returned is 6.18 or lower (e.g., 6.18, 6.17, 6.0, etc.)
  3. Confirm vulnerability applies to this installation
    This XSS vulnerability affects any WordPress site with MaxButtons plugin versions 6.18 or below, regardless of specific configuration. The vulnerability is present in the plugin code itself.
    Affected if Installed version is <= 6.18

You are affected if MaxButtons plugin is installed and the version number is 6.18 or lower.

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
Upgrade available Upgrade to a release after 6.18
Interim mitigation

Update MaxButtons (both free and Pro versions) to version 6.19 or later to remediate the vulnerability.

Fix this in Maxbuttons Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA0.5 h
3.5 hours of engineering $750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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