Security readout for executives and security teams
Plain-English summary
A vulnerable WordPress plugin can be tricked into changing usernames while an administrator is logged in. That could include changing the admin username. The issue is not marked as actively exploited here, but it can disrupt account management and create security confusion on affected WordPress sites.
Executive priority
Treat this as a moderate WordPress hygiene issue. It is unlikely to justify emergency response by itself, but affected sites should be updated promptly because administrator account changes can create operational disruption and incident-response confusion.
Technical view
Easy Username Updater before 1.0.5 lacks CSRF protection on username-change functionality. A CSRF condition could cause a logged-in administrator to submit an unintended username change affecting any user, including administrators. The weakness maps to CWE-352 and has CVSS 3.1 score 5.7.
Likely exposure
Exposure is limited to WordPress sites running Easy Username Updater versions before 1.0.5, especially where administrators browse while authenticated. The provided evidence does not identify broader affected products or CPEs.
Exploitation context
The source bundle does not show KEV listing or other evidence of active exploitation. The attack depends on a logged-in administrator interacting with attacker-influenced content, so practical exploitation is more conditional than unauthenticated server-side bugs.
Researcher notes
Evidence is concise and mostly centers on the CVE description and WPScan reference. The bundle states versions before 1.0.5 are affected, while no exploit proof, patch details beyond version boundary, or live exploitation evidence is provided.
Mitigation direction
- Update Easy Username Updater to version 1.0.5 or later.
- Review vendor and WPScan guidance for any additional remediation notes.
- Restrict administrator browsing from active WordPress admin sessions.
- Remove the plugin if username editing is not operationally required.
- Monitor admin account username changes for unauthorized activity.
Validation and detection
- Inventory WordPress sites for the Easy Username Updater plugin.
- Confirm installed plugin versions are 1.0.5 or later.
- Review WordPress audit logs for unexpected username changes.
- Verify administrative users and usernames match expected records.
- Check whether any affected site still relies on the vulnerable plugin path.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-352: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2022-2355 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.7 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:N0.55.2Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5.7MediumVector: CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://wpscan.com/vulnerability/426b5a0f-c16d-429a-9396-b3aea7922826CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Cross-Site Request Forgery (CSRF)
Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.