PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-16602 Passster CVE debrief

The Passster WordPress plugin before 4.3.6 does not perform a post-status check before returning post content from an unauthenticated REST endpoint, allowing unauthenticated users to disclose the content of non-public posts on sites with a configured captcha provider. This vulnerability affects site administrators who use the Passster WordPress plugin. The vulnerability allows attackers to access sensitive information, potentially leading to further exploitation. Evidence is limited; primary official records indicate a vulnerability in Passster WordPress plugin before 4.3.6 allowing unauthenticated content disclosure of non-public posts.

Vendor
Passster
Product
Passster WordPress plugin
CVSS
HIGH 7.5
CISA KEV
Not listed in stored evidence
Original CVE published
2026-08-05
Original CVE updated
2026-08-26
Advisory published
2026-08-05
Advisory updated
2026-08-26

Who should care

Site administrators using Passster WordPress plugin versions before 4.3.6 should be aware of potential content disclosure risks. They should prioritize updating to the latest version and review site configurations for captcha providers to prevent potential content disclosure. Additionally, security teams and vulnerability management teams should be aware of this vulnerability and its potential impact on their organization's assets.

Technical summary

The Passster WordPress plugin before 4.3.6 does not perform a post-status check before returning post content from an unauthenticated REST endpoint, allowing unauthenticated users to disclose the content of non-public posts on sites that have a captcha provider configured. This vulnerability allows attackers to access sensitive information, potentially leading to further exploitation. The vulnerability affects sites using Passster WordPress plugin versions before 4.3.6 and allows unauthenticated users to access sensitive information. Site administrators should verify the configuration of captcha providers and review site logs for potential content disclosure attempts.

Defensive priority

Sites using Passster WordPress plugin versions before 4.3.6 should prioritize updating to the latest version to prevent potential content disclosure.

Recommended defensive actions

  • Update Passster WordPress plugin to version 4.3.6 or later
  • Review site configurations for captcha providers
  • Monitor for potential content disclosure attempts
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
  • Review compensating controls for exposed systems while remediation is scheduled and verified
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review
  • Track exceptions, retest remediated assets, and close the item only after evidence is documented

Evidence notes

The Passster WordPress plugin before 4.3.6 does not perform a post-status check before returning post content from an unauthenticated REST endpoint. Evidence is limited; primary official records indicate a vulnerability in Passster WordPress plugin before 4.3.6 allowing unauthenticated content disclosure of non-public posts. Site administrators should verify the configuration of captcha providers and review site logs for potential content disclosure attempts.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-16602 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-16602

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-16602 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-16602

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.