WordPress plugin · content-protector
Is Passster safe?
Safe on 4.3.20 or newer.
The current version, 4.3.20, is past every affected range on record (19 of 19 records list one). Keep it updated and you’re clear of them.
- Flaws on record
- 19
- High or critical
- 5
- Exploited
- none
- Current version
- 4.3.20
- Last updated
- Oct 23, 2026
- Active installs
- 10,000+
Every recorded flaw
- Oct 16, 2026Passster: Missing AuthorizationCVE-2026-110896 · affects up to 4.3.18 · reported by PatchstackMedium 5.3
- Sep 11, 2026Unauthenticated Broken Access Control in Passster <= 4.3.13 versions.CVE-2026-62114 · affects up to 4.3.13 · reported by PatchstackMedium 5.3
- Sep 2, 2026Passster: Has a flaw in its global protection checksCVE-2025-15490 · fixed in 4.2.26 · reported by WPScanMedium 5.3
- Sep 2, 2026Passster: Does not handle input properly in an AJAX actionCVE-2025-15489 · fixed in 4.2.24 · reported by WPScanMedium 5.3
- Aug 21, 2026Passster: Does not correctly match its own public endpoint pathsCVE-2026-17559 · fixed in 4.3.9 · reported by WPScanMedium 5.3
- Aug 6, 2026Passster: Does not restrict low-privilege users holding the edit_posts capability from reading globally password-protected content through the WordPress core REST APICVE-2025-15674 · fixed in 4.3.7 · reported by WPScanLow 2.7
- Aug 5, 2026Passster: Outputs password-protected block content in the public page response before verifying the passwordCVE-2026-16604 · fixed in 4.3.6 · reported by WPScanHigh 7.5
- Aug 5, 2026Passster: Does not enforce its category-based content protection on the WordPress REST APICVE-2026-16603 · fixed in 4.3.6 · reported by WPScanHigh 7.5
- Aug 5, 2026Passster: Does not perform a post-status check before returning post content from an unauthenticated REST endpointCVE-2026-16602 · fixed in 4.3.6 · reported by WPScanHigh 7.5
- Feb 3, 2026Passster: Missing AuthorizationCVE-2026-25036 · affects up to 4.2.25 · reported by PatchstackMedium 6.5
- Jan 28, 2026Passster – Password Protect Pages and Content: Stored Cross-Site ScriptingCVE-2025-14865 · affects up to 4.2.24 · reported by WordfenceMedium 6.4
- Dec 18, 2025Passster: Insertion of Sensitive Information Into Sent DataCVE-2025-64218 · affects up to 4.2.19 · reported by PatchstackHigh 7.5
- Sep 22, 2025Passster: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')CVE-2025-57926 · affects up to 4.2.18 · reported by PatchstackMedium 6.5
- Jan 7, 2025Passster – Password Protect Pages and Content: Sensitive Information ExposureCVE-2024-11282 · affects up to 4.2.10 · reported by WordfenceMedium 5.3
- Apr 9, 2024Passster: Stored Cross-Site ScriptingCVE-2024-2026 · affects up to 4.2.6.4 · reported by WordfenceMedium 6.4
- Feb 28, 2024Passster – Password Protect Pages and Content: Sensitive Information ExposureCVE-2024-0616 · affects up to 4.2.6.2 · reported by WordfenceMedium 5.3
- Jan 23, 2023Passster: Does not properly check for passwordCVE-2021-24881 · fixed in 3.5.5.9 · reported by WPScanHigh 7.5
- Jan 23, 2023Passster: Does not escape the area parameter of its shortcodeCVE-2021-24837 · fixed in 3.5.5.8 · reported by WPScanMedium 5.4
- Oct 17, 2022Passster: Stores the password inside a cookie named "passster" using base64 encoding methodCVE-2022-3206 · fixed in 3.5.5.5.2 · reported by WPScanMedium 5.9
Records come from the National Vulnerability Database, published by the researchers who found each flaw (Wordfence, Patchstack, WPScan and others); exploited status from CISA; exploit odds from FIRST’s EPSS; current version, installs and closures from wordpress.org, checked daily. Want every plugin on your site checked at once? Run the free website check.
Weekly security brief
The flaws that hit local websites, every Friday.
One short email: what got exploited this week, which WordPress plugins broke, and what to check. Unsubscribe in one click.
Tell us what you're building.
A website, your marketing, a security check, an app, or the thing you've been running out of a spreadsheet for three years. A few lines is plenty.
Not ready to talk yet? Run the free website check and see what Google sees.