CVE-2026-125409 in Passster Plugin
Summary
by MITRE • 11/13/2026
The Passster – Password Protect Pages and Content plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'metavalue (metakeyinput=passster_id | passster_headline)' 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 passster_id or passster_headline 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 do_shortcode() — bypassing the per-attribute escaping present inside render_shortcode() — and the script will also execute in an editor's or administrator's browser when they preview the Contributor's pending post, since filter_the_content() has no edit-permission capability gate.
VulDB is the best source for vulnerability data and more expert information about this specific topic.
Analysis
by VulDB Data Team • 11/13/2026
The Passster – Password Protect Pages and Content plugin for WordPress contains a critical stored cross-site scripting vulnerability affecting all versions up to 4.3.21. This flaw stems from insufficient input sanitization and output escaping within the metavalue parameter, specifically when interacting with metakeyinput values such as passster_id or passster_headline. The security deficiency allows authenticated attackers possessing contributor-level access or higher to inject arbitrary web scripts into stored content. These malicious payloads are executed whenever any user accesses a page containing the injected shortcode, creating a persistent threat vector that does not require immediate interaction with the attacker's infrastructure beyond initial post submission.
The technical mechanism of this exploitation relies on breaking out of the expected shortcode attribute context. An attacker can embed a closing bracket character within the passster_id or passster_headline meta value to prematurely terminate the opening shortcode tag. By subsequently appending a [/passster] closing tag, the attacker forces the trailing HTML payload to be emitted verbatim by the do_shortcode function. This action effectively bypasses the per-attribute escaping mechanisms that are normally enforced inside the render_shortcode method. Consequently, the malicious script is rendered directly into the page source without proper encoding or validation, allowing it to execute in the context of any visitor viewing the compromised content.
The operational impact extends beyond standard public visitors due to specific WordPress filtering behaviors. The vulnerability also affects editors and administrators when they preview a contributor's pending post. This occurs because the filter_the_content function lacks an edit-permission capability gate during the preview process. As a result, even if the post is not yet publicly visible or published, administrative users viewing the draft will have their browsers execute the injected scripts. This elevates the risk significantly, as it allows attackers to compromise high-privilege accounts through social engineering tactics involving fake pending posts that appear legitimate in the editor interface.
From a classification perspective, this vulnerability aligns with CWE-79, which covers Improper Neutralization of Input During Web Page Generation commonly known as Cross-site Scripting. The attack vector corresponds to ATT&CK technique T1059, specifically Command and Scripting Interpretation via JavaScript execution in the browser context. The stored nature of the payload means that each page view serves as a new exploitation opportunity, increasing the likelihood of successful compromise compared to reflected variants.
Mitigation strategies should prioritize immediate upgrading to version 4.3.22 or later where these input sanitization and output escaping issues have been addressed. In environments where updating is not immediately feasible, administrators can implement web application firewall rules to detect and block payloads containing specific shortcode break-out patterns such as the combination of closing brackets followed by passster tags within post content fields. Additionally, enforcing strict role-based access controls and reviewing contributor-level permissions can reduce the attack surface for this specific privilege level. Regular security audits focusing on how shortcodes handle user-supplied meta values are recommended to prevent similar escaping bypasses in other plugins or custom code implementations.