CVE-2026-123656 json
ProfilePress < 4.17.6 - Unauthenticated Restricted Content Disclosure via REST API
published yesterday modified yesterday also EUVD-2026-123194
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 6%
- public exploits
- 0
- none known
Summary
The ProfilePress WordPress plugin before 4.17.6 does not correctly evaluate some of its content protection rule conditions when content is rendered outside the main query, allowing unauthenticated users to read the content of pages protected by such rules via the REST API.
Patch / fix
- Unknown ProfilePress 4.17.6
Is CVE-2026-123656 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
0.17% chance of exploitation in the next 30 days, higher than 6% of all scored CVEs (FIRST EPSS, 2026-11-11).
Exploits and checks
- wpscan.com https://wpscan.com/vulnerability/5a670095-e8c7-4317-a929-a896d01ee648/ referenced PoC, tagged "exploit" by a source, unverified
Affected products
- Unknown ProfilePress
Classification
- Weakness
-
- CWE-284 Improper Access Control
- Technology feeds
References
-
wpscan.com
/vulnerability/5a670095-e8c7-4317-a929-a896d01ee648/
exploit, vdb-entry, technical-description
Sources
- CVE List CVE-2026-123656
- NVD CVE-2026-123656
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.