Security readout for executives and security teams
Plain-English summary
CVE-2022-31475 affects the GiveWP WordPress plugin version 2.20.2 and earlier. A logged-in user with the plugin’s custom role could abuse the export function to read files they should not access. The main business risk is exposure of sensitive site data or configuration files, not service disruption.
Executive priority
Treat this as a moderate-priority WordPress plugin exposure issue. It is not described as actively exploited, but it can expose sensitive files if privileged GiveWP access is compromised or misassigned.
Technical view
The issue is an authenticated arbitrary file read in GiveWP’s export functionality for versions <= 2.20.2. CVSS 3.1 is 5.5 with network access, low complexity, high privileges required, no user interaction, high confidentiality impact, low integrity impact, and no availability impact. CWE mappings include path traversal, improper access control, and exposed file/resource weaknesses.
Likely exposure
Exposure is limited to WordPress sites running GiveWP <= 2.20.2 where a user has the relevant custom plugin role or that account is compromised. Public unauthenticated exposure is not supported by the supplied sources.
Exploitation context
The supplied sources do not show CISA KEV listing or active exploitation. Abuse requires authenticated high-privilege plugin access, which makes compromised admin-like accounts, over-assigned GiveWP roles, or malicious insiders the main practical scenarios.
Researcher notes
Evidence supports authenticated arbitrary file read only for GiveWP <= 2.20.2. Do not assume unauthenticated exploitation or broad WordPress core impact. Patch details are incomplete in the supplied bundle, so remediation should be tied to vendor confirmation.
Mitigation direction
- Inventory WordPress sites using GiveWP and identify versions <= 2.20.2.
- Check GiveWP vendor guidance and update beyond the affected range when a confirmed fix is available.
- Remove unnecessary GiveWP custom role assignments and export permissions.
- Review WordPress accounts for weak, shared, or stale privileged access.
- Monitor for unusual export activity involving privileged GiveWP users.
Validation and detection
- Confirm installed GiveWP versions across production and staging WordPress sites.
- List users assigned GiveWP custom roles or export-related capabilities.
- Review plugin changelog or vendor advisory for the fixed version before closing remediation.
- Check WordPress and web server logs for unusual authenticated export requests.
- Verify least-privilege access after remediation.
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-22: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. 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 lookupCWE-284: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. 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 lookupCWE-552: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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 lookupFile access behavior lookup
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2022-31475 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.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:L/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:L/PR:H/UI:N/S:U/C:H/I:L/A:N1.24.2Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5.5MediumVector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:L/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://wordpress.org/plugins/give/#developersCVE reference · x_refsource_CONFIRM
- https://patchstack.com/database/vulnerability/give/wordpress-givewp-plugin-2-20-2-authenticated-arbitrary-file-read-via-export-function-vulnerabilityCVE reference · x_refsource_CONFIRM
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.
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Improper Access Control
Improper Access Control represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Files or Directories Accessible to External Parties
Files or Directories Accessible to External Parties represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.