dbcve.org
PasssterWordPress extension · Wpchill

CVE-2024-2026

MEDIUM · 5.4 CVSS v3.1 Published 2024-04-09
Fix available
A fix is available. Upgrade to 4.2.6.5 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 Passster plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's content_protector shortcode in all versions up to, and including, 4.2.6.4 due to insufficient input sanitization and output escaping on user supplied attributes. 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 confidence

The Passster WordPress plugin contains a stored XSS vulnerability in its content_protector shortcode. Authenticated attackers with contributor-level permissions can inject arbitrary JavaScript through unsanitized shortcode attributes, which executes when other users view affected pages.

MitigationUpdate the Passster plugin to version 4.2.6.5 or later. Until a patch is available, implement input sanitization using sanitize_text_field() and output escaping with esc_html() or esc_attr() on all shortcode attributes.

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
PasssterWordPress extension
Affected:< 4.2.6.5

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

CVSS:3.1/AV:N/AC:L/PR:L/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. Identify Passster plugin installation
    In WordPress admin, go to Plugins > Installed Plugins and locate 'Passster' by Wpchill. Note the installed version number displayed next to the plugin name.
    Affected if The plugin is installed and the version shown is below 4.2.6.5 (for example, 4.2.6, 4.2.5, 4.2.0, etc.)
  2. Scan for content_protector shortcode usage
    Use WordPress search or a database query to find posts, pages, or custom post types containing the shortcode [content_protector] or [passster] in the post_content column of the wp_posts table.
    Affected if Any posts or pages contain the content_protector shortcode, creating potential attack surface for XSS injection.
  3. Inspect shortcode attributes for unsanitized input
    Examine the saved content of posts containing the content_protector shortcode. Look at each attribute (such as id, password, heading, button_text) and verify whether the values contain HTML, JavaScript, or script tags (for example, <script>alert(1)</script>).
    Affected if Any shortcode attribute contains raw HTML, JavaScript tags, or unescaped special characters that could execute as code when the page is viewed.
  4. Review contributor-level user accounts
    Go to Users > All Users in WordPress admin. Identify any users with the Contributor role, as this permission level can edit and publish content where the shortcode would execute.
    Affected if There are one or more contributor-level users in the WordPress installation who could potentially inject malicious shortcode attributes.
  5. Check for stored XSS execution in browser
    As an administrator, view a page containing the content_protector shortcode while logged in. Inspect the page source or use browser developer tools to see if any shortcode attributes render as executable JavaScript rather than escaped text.
    Affected if When viewing a page with the shortcode, raw HTML or JavaScript from shortcode attributes renders and executes in the browser.

You are affected if Passster plugin version is below 4.2.6.5 AND the content_protector shortcode is used on your site with any user input that may not have been sanitized.

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
Upgrade available Upgrade to 4.2.6.5 or later
Fixed in 4.2.6.5
Interim mitigation

Update the Passster plugin to version 4.2.6.5 or later. Until a patch is available, implement input sanitization using sanitize_text_field() and output escaping with esc_html() or esc_attr() on all shortcode attributes.

Recommended fix High confidence

4.2.6.5

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the Passster plugin in the list
  4. 4. If an update is available, click 'Update Now' to update to version 4.2.6.5
  5. 5. Alternatively, go to Plugins > Add New > Upload Plugin and upload version 4.2.6.5 from the WordPress plugin repository
  6. 6. Verify the plugin version after update to confirm 4.2.6.5 is installed

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

Fix this in Passster Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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