CVE-2026-12102 json
UsersWP <= 1.2.63 - Insecure Direct Object Reference to Authenticated (Editor+) Arbitrary User Avatar/Banner Reset via 'user_id' Parameter
published 4mo ago modified 4mo ago also EUVD-2026-37860
- cvss
- 2.7
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 19%
- public exploits
- 0
- none known
Summary
The UsersWP – Front-end login form, User Registration, User Profile & Members Directory plugin for WP plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 1.2.63 via the 'user_id' parameter due to missing validation on a user controlled key. This makes it possible for authenticated attackers, with editor-level access and above, to reset and permanently delete the avatar or banner image of any arbitrary user, including administrators, by clearing their avatar_thumb or banner_thumb metadata in the uwp_usermeta table.
Patch / fix
Is CVE-2026-12102 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
- partial
- Assessed
- 4mo ago
Exploit prediction
0.27% chance of exploitation in the next 30 days, higher than 19% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 2.7 | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:N |
Affected products
- stiofansisland UsersWP – Front-end login form, User Registration, User Profile & Members Directory plugin for WP
Classification
- Weakness
-
- CWE-639 Authorization Bypass Through User-Controlled Key
- Technology feeds
References
- github.com /AyeCode/userswp/commit/0e69f967578904cc26fadd0206270d50b7420298
- wordfence.com /threat-intel/vulnerabilities/id/7115756e-69fa-42fe-bde3-a36e34d4bae3?source=cve
- plugins.trac.wordpress.org /browser/userswp/tags/1.2.63/includes/class-forms.php#L371
- plugins.trac.wordpress.org /browser/userswp/tags/1.2.63/includes/class-forms.php#L389
- plugins.trac.wordpress.org /browser/userswp/tags/1.2.63/includes/class-forms.php#L89
- plugins.trac.wordpress.org /browser/userswp/tags/1.2.63/includes/class-userswp.php#L574
- plugins.trac.wordpress.org /browser/userswp/tags/1.2.63/includes/class-profile.php#L1739
- plugins.trac.wordpress.org /browser/userswp/tags/1.2.61/includes/class-forms.php#L371
- plugins.trac.wordpress.org /browser/userswp/tags/1.2.61/includes/class-forms.php#L389
- plugins.trac.wordpress.org /browser/userswp/tags/1.2.61/includes/class-forms.php#L89
- plugins.trac.wordpress.org /browser/userswp/tags/1.2.61/includes/class-userswp.php#L574
- plugins.trac.wordpress.org /browser/userswp/tags/1.2.61/includes/class-profile.php#L1739
Sources
- CVE List CVE-2026-12102
- NVD CVE-2026-12102
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.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.