CVE-2026-13152 json
Custom Fields Account Registration For WooCommerce < 1.4 - Unauthenticated Privilege Escalation
published 3mo ago modified 3mo ago also EUVD-2026-49069
- cvss
- 8.1
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 38%
- public exploits
- 0
- none known
Summary
The Custom Fields Account Registration For Woocommerce WordPress plugin before 1.4 does not prevent its custom registration fields from writing to the user capabilities meta key on sites that use a non-default database table prefix, so an unauthenticated user who registers an account can be granted the administrator role when a correspondingly named field has been configured.
Patch / fix
- Unknown Custom Fields Account Registration For Woocommerce 1.4
Is CVE-2026-13152 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 FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 3mo ago
Exploit prediction
0.44% chance of exploitation in the next 30 days, higher than 38% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- wpscan.com https://wpscan.com/vulnerability/36aaba38-3143-4e80-8386-748632ff6704/ referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 8.1 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H |
| CNA | 3.1 | 8.1 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected products
- Unknown Custom Fields Account Registration For Woocommerce
Classification
- Weakness
-
- CWE-269 Improper Privilege Management
- Technology feeds
References
-
wpscan.com
/vulnerability/36aaba38-3143-4e80-8386-748632ff6704/
exploit, vdb-entry, technical-description
Sources
- CVE List CVE-2026-13152
- NVD CVE-2026-13152
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.