CVE-2026-15301
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 · uneditedThe BuddyHolis TableSearch plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘placeholder’ parameter in all versions up to, and including, 1.1.0 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
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 confidenceThe BuddyHolis TableSearch WordPress plugin (versions up to 1.1.0) fails to properly sanitize the 'placeholder' parameter during input and escape it during output, allowing authenticated users with Contributor-level permissions or higher to inject malicious JavaScript. This stored XSS payload executes whenever any user accesses pages containing the affected search component.
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
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Verify plugin installationCheck if the BuddyHolis TableSearch plugin is present in the WordPress plugins directory (wp-content/plugins/ or via WP Admin > Plugins)Affected if The plugin is installed and active in WordPress
-
Identify installed versionCheck the plugin header in its main PHP file (typically tablesearch.php or similar in wp-content/plugins/tablesearch/) for the Version field, or view the plugin details in WP Admin > PluginsAffected if The reported version is 1.1.0 or any version up to 1.1.0
-
Review placeholder parameter handlingExamine the plugin PHP code where the placeholder parameter is processed (search for $_POST, $_GET, or $_REQUEST handling of 'placeholder'), and verify if sanitize_text_field() or similar sanitization is applied on input, and esc_attr() or esc_html() is applied on outputAffected if The code processes the placeholder parameter without proper input sanitization (sanitize_text_field) AND output escaping (esc_attr or esc_html)
-
Confirm user role accessCheck if any user account with Contributor-level or higher permissions exists on the WordPress site, as this role is required to exploit the vulnerabilityAffected if At least one user with Contributor, Author, Editor, or Administrator role exists
The environment is affected if the BuddyHolis TableSearch plugin version 1.1.0 or lower is installed, the placeholder parameter lacks proper sanitization/escaping in the code, and users with Contributor-level or higher access exist on the site.
Generated from the published advisory. Verify against your own configuration.
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 dataUpdate to a patched version if available; otherwise, implement proper input sanitization using sanitize_text_field() and output escaping with esc_attr() or esc_html() on the placeholder parameter in the plugin code.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2026-15301 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-15301 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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