Security readout for executives and security teams
Plain-English summary
This is a medium-severity CSRF issue in miniOrange WordPress REST API Authentication plugin versions 2.4.0 and earlier. An attacker could potentially abuse a logged-in user’s browser to make unintended changes or disrupt limited functionality. The provided sources do not describe stolen data, active exploitation, or a named fixed version.
Executive priority
Handle this as a normal vulnerability-management item, not an emergency based on current evidence. Prioritize internet-facing WordPress sites and any site where the plugin controls sensitive API authentication behavior.
Technical view
CVE-2022-45073 is CWE-352 CSRF affecting REST API Authentication for WordPress <= 2.4.0. CVSS v3.1 is 5.4: network reachable, low complexity, no attacker privileges, user interaction required, with low integrity and availability impact and no confidentiality impact.
Likely exposure
Exposure is limited to WordPress sites running the miniOrange REST API Authentication plugin at version 2.4.0 or earlier. Sites not using this plugin, or using versions outside the affected range, are not shown as affected by the provided sources.
Exploitation context
The CVE is not listed as KEV, and the provided sources do not state active exploitation. The attack class requires user interaction, typically a logged-in user visiting attacker-controlled content, but the sources do not provide operational exploit details.
Researcher notes
The source bundle identifies the vulnerability class, affected version range, CVSS vector, and CWE, but does not include exploit details, a fixed version, or detailed vulnerable endpoints. Treat remediation specifics as vendor-dependent until confirmed from miniOrange or Patchstack guidance.
Mitigation direction
- Inventory WordPress sites for the REST API Authentication plugin and its version.
- Prioritize sites running version 2.4.0 or earlier for remediation review.
- Check miniOrange and Patchstack guidance for a confirmed fixed version or mitigation.
- Apply vendor-approved updates through normal WordPress change control.
- Limit administrative browsing from authenticated WordPress sessions where practical.
Validation and detection
- Confirm plugin presence and exact version on each WordPress site.
- Verify affected systems are running version 2.4.0 or earlier before prioritizing.
- Review WordPress audit logs for unexpected settings or plugin configuration changes.
- Recheck vendor or Patchstack advisories for fixed-version details.
- Document whether each site is affected, remediated, or not applicable.
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-45073 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.4 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L
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:L/PR:N/UI:R/S:U/C:N/I:L/A:L2.82.5Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5.4MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L
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.