LiveActive security incident?Get immediate response
CVE Record

CVE-2022-37403: WordPress Add User Role plugin <= 0.0.1 - Authenticated Stored Cross-Site Scripting (XSS) vulnerability

Authenticated (admin+) Stored Cross-Site Scripting (XSS) vulnerability in Nikhil Vaghela's Add User Role plugin <= 0.0.1 at WordPress.

MediumCVSS 4.8Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This is a stored cross-site scripting issue in the WordPress Add User Role plugin version 0.0.1 and earlier. An authenticated administrator-level user could store script content that later runs in another user’s browser. The business risk is constrained by high privileges required, but affected sites should still treat it as a real integrity and account-risk issue.

Executive priority

Handle during normal vulnerability remediation, faster for public or business-critical WordPress sites. The required administrator privileges reduce likelihood, but stored XSS can still support account compromise, content tampering, and trust damage if an admin account is misused.

Technical view

CVE-2022-37403 is CWE-79 in Nikhil Vaghela’s Add User Role WordPress plugin <= 0.0.1. The CVSS 3.1 score is 4.8 with PR:H and UI:R, indicating exploitation requires administrator-level authentication and user interaction. Impact is limited confidentiality and integrity loss with no availability impact stated.

Likely exposure

Exposure is limited to WordPress sites that installed Add User Role version 0.0.1 or earlier. The source bundle does not identify affected core WordPress, other plugins, or downstream products.

Exploitation context

The CVE is not listed as KEV, and the provided sources do not cite active exploitation. The issue is stored XSS, but no public exploit status or weaponized details are provided in the bundle.

Researcher notes

Evidence supports authenticated admin-plus stored XSS only. The CVSS vector shows network access, low complexity, high privileges, required user interaction, changed scope, low confidentiality and integrity impact, and no availability impact. No fixed version is named in the supplied sources.

Mitigation direction

  • Inventory WordPress sites for the Add User Role plugin.
  • Disable and remove the plugin where it is not required.
  • Check vendor and WordPress plugin guidance for fixed or retired status.
  • Restrict administrator access to trusted users only.
  • Review stored plugin-managed data before re-enabling production use.

Validation and detection

  • Confirm whether Add User Role is installed on each WordPress site.
  • Verify whether the installed version is 0.0.1 or earlier.
  • Identify administrator accounts with access to affected plugin functions.
  • Review administrative activity for unexpected content or settings changes.
  • Document compensating controls if no vendor fix is available.
Prepared
Confidence
high
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · medium confidence lookup

CWE-79: 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 lookup
cve · low confidence lookup

CVE-2022-37403 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
4.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N

Official CVE source material

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.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We 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.

ScoreVersionSeverityVectorExploitImpactSource
4.8CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N1.72.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

4.8Medium
CVSS 3.1 vector shape for CVE-2022-37403Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Nikhil VaghelaAdd User Role (WordPress plugin)<= 0.0.1Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.