The ProfilePress WordPress plugin before 4.18.1 does not atomically consume the source subscription when processing a
Source GCVE Database
Not known to be exploited : upgrade to 4.18.1 soon.
Data as of 18 Nov 2026, 08:19 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.18.1
Exploitation evidence
Disclosed: evidence found.
CVE published 18 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 17 Nov 2026.
What to do
Upgrade ProfilePress (WordPress plugin) to 4.18.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| ProfilePress | Affected
| Fixed in
|
AI-suggested
Upgrade the ProfilePress WordPress plugin to version 4.18.1 or later, where this issue is fixed. No other mitigation guidance is provided. Patch status is confirmed by the version number in the description.
Description
The ProfilePress WordPress plugin versions before 4.18.1 contain a flaw in processing membership plan changes. The plugin does not atomically consume the source subscription, which allows customers to perform concurrent plan-change checkouts on a single paid subscription. This can result in multiple active memberships being obtained for the price of one.