CVE-2026-125409: Passster <= 4.3.21 - Authenticated (Contributor+) Stored Cross-Site Scripting via 'metavalue' Parameter

Published Nov 13, 2026
·
Updated

The Passster – Password Protect Pages and Content plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'metavalue (metakeyinput=passsterid | passsterheadline)' parameter in all versions up to, and including, 4.3.21 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. A Contributor can break out of the shortcode attribute context by embedding a ] character in the passsterid or passsterheadline meta value to prematurely close the opening shortcode tag, then append a [/passster] closing tag so that the trailing HTML payload is emitted verbatim by doshortcode() — bypassing the per-attribute escaping present inside rendershortcode() — and the script will also execute in an editor's or administrator's browser when they preview the Contributor's pending post, since filterthecontent() has no edit-permission capability gate.

Affected Software

1 affected component
wordpress/passster<=4.3.21

Event History

Nov 13, 2026
CVE Published
via MITRE·09:35 AM
Data Sourced
via MITRE·09:35 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·10:17 AM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Who can exploit this issue?

An authenticated WordPress user with Contributor-level access or higher can exploit it. The attacker needs to be able to create or edit content containing the affected Passster metadata values.

2

What is required for exploitation?

The attacker must supply a crafted passster_id or passster_headline metavalue containing a ] character to escape the shortcode attribute context, then add a [/passster] closing tag and HTML script payload. No victim interaction is required for injection, but the stored script runs when someone accesses the affected page.

3

Can administrators be affected even if the malicious post is not published?

Yes. An editor or administrator can trigger the script by previewing a Contributor's pending post, because the content filter does not require edit-permission checks before rendering the injected content.

4

How can I identify potentially affected content?

Review content created or editable by Contributor-level users for Passster passster_id or passster_headline values containing a ] character, especially where a closing [/passster] tag is followed by unexpected HTML or script content. Versions up to and including 4.3.21 are affected.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203