CVE-2026-25015

UsersWP <= 1.2.53 - Cross-Site Request Forgery

2026-01-28 00:00
Tristan Jay Neale

Strategic Overview

Status
Patched in 1.2.54
Affected Plugin
UsersWP – Front-end login form, User Registration, User Profile & Members Directory plugin for WP
Affected Version
<= 1.2.53
CVSS
4.3Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2026-25015
View all UsersWP – Front-end login form, User Registration, User Profile & Members Directory plugin for WP vulnerabilities

At a glance

CVE-2026-25015 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the UsersWP WordPress plugin, affecting versions <= 1.2.53. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 1.2.54; sites on affected versions should update now. Disclosed January 2026, reported by Tristan Jay Neale.

Vulnerability Overview

The UsersWP – Front-end login form, User Registration, User Profile & Members Directory plugin for WP plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.2.53. This is due to missing or incorrect nonce validation on the ajax_avatar_banner_upload() function. This makes it possible for unauthenticated attackers to upload banners for other users granted they can trick an authenticated site user into performing an action such as clicking on a link.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site.

CWE-352: Cross-Site Request Forgery (CSRF)

UsersWP <= 1.2.53 carries this weakness at ajax_avatar_banner_upload(), and reaching it takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.

An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For UsersWP the fix is 1.2.54: builds <= 1.2.53 are affected, anything from 1.2.54 onward is not.

Remediation

Update to version 1.2.54, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to UsersWP: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: UsersWP 1.2.54 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-25015https://www.wordfence.com/threat-intel/vulnerabilities/id/313b5634-20c6-4666-be96-ce59fa4366achttps://nvd.nist.gov/vuln/detail/CVE-2026-25015

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C