← WordPress Vulnerabilities
WordPress security by component

Passster

Passster is a WordPress component with 5 published CVE records in this archive. The latest tracked vulnerability was published Feb 03, 2026; the highest CVE/CNA score is 7.5.

Plugin slug: content-protector

CVE-2026-25036: Passster: A security weakness

Passster is affected by a security weakness. Exposure depends on how the affected operation is made reachable by the site. The resulting impact depends on how the affected component exposes the vulnerable operation.

PublishedFeb 03, 2026
Safe version guidanceSee mitigation notes
Safe version
Feb 03, 2026 CVE-2026-25036
Passster: A security weakness
Passster is affected by a security weakness. Exposure depends on how the affected operation is made reachable by the site. The resulting impact depends on how the affected component exposes the vulnerable operation.
See mitigation notes
CVE6.5
NVDPending
Jan 28, 2026 CVE-2025-14865
Passster – Password Protect Pages and Content: Cross-site scripting
Passster – Password Protect Pages and Content is affected by cross-site scripting. Exploitation requires at least contributor-level access. Injected script can execute in the affected site's origin when the vulnerable output is viewed.
See mitigation notes
CVE6.4
NVDPending
Dec 18, 2025 CVE-2025-64218
Passster: A security weakness
Passster is affected by a security weakness. Exposure depends on how the affected operation is made reachable by the site. The resulting impact depends on how the affected component exposes the vulnerable operation.
See mitigation notes
CVE7.5
NVDPending
Sep 22, 2025 CVE-2025-57926
Passster: Cross-site scripting
Passster is affected by cross-site scripting. Exposure depends on how the affected operation is made reachable by the site. Injected script can execute in the affected site's origin when the vulnerable output is viewed.
See mitigation notes
CVE6.5
NVDPending
Apr 09, 2024 CVE-2024-2026
Passster: Cross-site scripting
Passster is affected by cross-site scripting. Exploitation requires at least contributor-level access. Injected script can execute in the affected site's origin when the vulnerable output is viewed.
See mitigation notes
CVE6.4
NVD5.4