Settings tampering via missing CSRF check
Published Jan 29, 2024 · Updated Jun 20, 2025
Cross-site request forgery in WordPress Users 1.4 and earlier allows remote attackers to change plugin settings through an administrator. The settings handler at /wp-admin/options-general.php?page=wordpress-users/wp-users.php accepts a POST with wpu_hidden=Y and attacker-chosen configuration values without validating a CSRF nonce. A logged-in Editor or Administrator must open attacker-controlled HTML, after which the forged request can alter roles, page IDs, avatar behavior, and other plugin configuration.
Summary
What happened
Cross-site request forgery in WordPress Users 1.4 and earlier allows remote attackers to change plugin settings through an administrator. The settings handler at /wp-admin/options-general.php?page=wordpress-users/wp-users.php accepts a POST with wpu_hidden=Y and attacker-chosen configuration values without validating a CSRF nonce. A logged-in Editor or Administrator must open attacker-controlled HTML, after which the forged request can alter roles, page IDs, avatar behavior, and other plugin configuration.
The record
- CVE
- CVE-2023-6390
- Published
- Jan 29, 2024
- Updated
- Jun 20, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-352, CAPEC-62, T1204.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 29, 2024CVE publishedPublication date reported by the CVE source.
- Jun 20, 2025Record 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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
- WPScan auto-submitting HTML proof of conceptproof of concept · validated
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