Security readout for executives and security teams
Plain-English summary
CVE-2022-33901 affects the MultiSafepay plugin for WooCommerce on WordPress. Versions 4.13.1 and earlier can allow an unauthenticated attacker to read files. The known impact is confidentiality exposure, not data modification or service outage, but payment-adjacent WordPress sites should treat it as a timely plugin hygiene issue.
Executive priority
Prioritize this for WordPress commerce environments, especially internet-facing stores. It is not rated critical and no active exploitation is cited, but unauthenticated file read can expose sensitive configuration or operational data if vulnerable sites remain online.
Technical view
The issue is an unauthenticated arbitrary file read in MultiSafepay plugin for WooCommerce <= 4.13.1, mapped to CWE-552. CVSS 3.1 is 5.3 with network attack vector, low complexity, no privileges, no user interaction, unchanged scope, and low confidentiality impact only.
Likely exposure
Exposure is limited to WordPress sites running the MultiSafepay plugin for WooCommerce at version 4.13.1 or earlier. Sites without this plugin, or with versions outside the affected range per vendor guidance, are not indicated as affected by the provided sources.
Exploitation context
The source bundle does not show CISA KEV listing or cited evidence of active exploitation. The CVSS vector indicates remote unauthenticated reachability, so internet-facing WordPress installations using the affected plugin deserve prioritized review even without confirmed exploitation.
Researcher notes
Do not assume broad WooCommerce exposure; the affected component is specifically MultiSafepay plugin for WooCommerce <= 4.13.1. The bundle does not provide exploit details, affected file paths, or a named fixed version, so validation should rely on version inventory and vendor-confirmed release notes.
Mitigation direction
- Inventory WordPress sites using the MultiSafepay WooCommerce plugin.
- Check vendor and Patchstack guidance for the fixed version.
- Update the plugin if a fixed release is available.
- Disable the plugin temporarily if update status cannot be confirmed.
- Review exposed WordPress sites for unnecessary file access permissions.
Validation and detection
- Confirm each site’s installed MultiSafepay plugin version.
- Flag versions 4.13.1 and earlier as affected.
- Verify remediation against the vendor plugin page or Patchstack entry.
- Check web logs for unusual unauthenticated file-read attempts.
- Document unaffected sites and evidence for audit tracking.
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-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-33901 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.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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:N/UI:N/S:U/C:L/I:N/A:N3.91.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5.3MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://wordpress.org/plugins/multisafepay/#developersCVE reference · x_refsource_CONFIRM
- https://patchstack.com/database/vulnerability/multisafepay/wordpress-multisafepay-plugin-for-woocommerce-plugin-4-13-1-unauthenticated-arbitrary-file-read-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.
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.