Profile-image changes via missing crop nonce validation
Published Feb 3, 2026 · Updated Feb 3, 2026
CSRF in AyeCode Ltd UsersWP 1.2.53 and earlier allows remote attackers to trigger profile or cover-image cropping through a forged request. The profile-image and cover-image crop workflow accepts requests without verifying a WordPress nonce in affected releases. Exploitation requires an authenticated user with profile-image permissions to open attacker-controlled content, limiting the result to an unwanted image-cropping action in that user's session.
Summary
What happened
CSRF in AyeCode Ltd UsersWP 1.2.53 and earlier allows remote attackers to trigger profile or cover-image cropping through a forged request. The profile-image and cover-image crop workflow accepts requests without verifying a WordPress nonce in affected releases. Exploitation requires an authenticated user with profile-image permissions to open attacker-controlled content, limiting the result to an unwanted image-cropping action in that user's session.
The record
- CVE
- CVE-2026-25015
- Published
- Feb 3, 2026
- Updated
- Feb 3, 2026
- Vendor
- AyeCode Ltd
- Product
- UsersWP
- Classifications
- CWE-352, CAPEC-62
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 3, 2026CVE publishedPublication date reported by the CVE source.
- Feb 3, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=n/a <=<= 1.2.53 changes=[{"at":"1.2.54","status":"unaffected"}]
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo