CVE-2026-123659VulnerabilityPublished 11 Nov 2026

The ProfilePress WordPress plugin before 4.17.6 does not restrict the role and user meta filters its member

Source GCVE Database

Compare

Authoritative record:CVE-2026-123659· Medium 5.3

Not known to be exploited · CVSS 5.3 Medium : upgrade to 4.17.6 when convenient.

Data as of 11 Nov 2026, 10:18 UTC

CVSS 3.1 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none

CVSS scores by source
CNA (WPScan)	CVSS 3.1	5.3

Patch: Available – fixed in 4.17.6

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

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.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-grj3-mv63-h3cw

What to do

Upgrade ProfilePress (WordPress plugin) to 4.17.6.

Affected software

Product	Affected	Fixed in
ProfilePress	Affected <4.17.6	Fixed in 4.17.6

AI-suggested

A fix is available in ProfilePress version 4.17.6. Users should update to this version or later to remediate the vulnerability. No other mitigation guidance is provided or necessary as the issue is resolved by the official patch.

Description

A vulnerability in the ProfilePress WordPress plugin versions before 4.17.6 allows unauthenticated users to bypass configured restrictions on role and user meta filters in member directories. This enables attackers to list accounts that were intended to be hidden and to access user meta values of those listed users.

Impact

The vulnerability allows unauthenticated attackers to access user account listings and user meta data that should be restricted. This results in information disclosure but does not affect integrity or availability. The CVSS score of 5.3 (medium severity) reflects the network attack vector, low complexity, no privileges required, and no user interaction needed, with confidentiality impact only.

Summary

The ProfilePress WordPress plugin prior to version 4.17.6 does not properly restrict role and user meta filters applied to its member directories. As a result, unauthenticated users can enumerate accounts that the administrator intended to hide and retrieve associated user meta information. This flaw arises from insufficient access control on these filters, leading to unauthorized information disclosure.

References

Community reviews

Loading reviews…