Unauthenticated protected-content inference via REST pagination
Published Jul 11, 2026 · Updated Jul 11, 2026
Sensitive information exposure in Caseproof Members 3.2.22 and earlier allows remote attackers to infer protected post content via REST requests. members_filter_protected_posts_for_rest removes protected posts after WordPress computes REST totals, leaving counts and pagination headers dependent on hidden matches. Content Permissions and REST hiding must apply to restricted posts; repeated keyword and page-size probes disclose existence and counts, not full post bodies.
Summary
What happened
Sensitive information exposure in Caseproof Members 3.2.22 and earlier allows remote attackers to infer protected post content via REST requests. members_filter_protected_posts_for_rest removes protected posts after WordPress computes REST totals, leaving counts and pagination headers dependent on hidden matches. Content Permissions and REST hiding must apply to restricted posts; repeated keyword and page-size probes disclose existence and counts, not full post bodies.
The record
- CVE
- CVE-2026-12426
- Published
- Jul 11, 2026
- Updated
- Jul 11, 2026
- Vendor
- Caseproof, LLC
- Product
- Members
- Classifications
- CWE-200, T1213
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 11, 2026CVE publishedPublication date reported by the CVE source.
- Jul 11, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=3.2.22
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo