The ProfilePress WordPress plugin before 4.17.6 does not correctly evaluate some of its content protection rule
Source GCVE Database
Not known to be exploited : upgrade to 4.17.6 soon.
Data as of 11 Nov 2026, 07:20 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in 4.17.6
Exploitation evidence
Disclosed: evidence found.
CVE published 11 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 10 Nov 2026.
What to do
Upgrade ProfilePress (WordPress plugin) to 4.17.6.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| ProfilePress | Affected
| Fixed in
|
AI-suggested
Upgrade the ProfilePress plugin to version 4.17.6 or later where this issue is fixed. No other mitigation guidance is provided.
Description
The ProfilePress WordPress plugin versions before 4.17.6 have a vulnerability where some content protection rules are not properly evaluated when content is rendered outside the main query. This flaw allows unauthenticated users to access protected page content via the REST API.