Security readout for executives and security teams
Plain-English summary
Several Addify WordPress and WooCommerce plugins had weak CSRF protections. An attacker could trick a logged-in site user into performing unwanted actions. The main business risk is unauthorized changes to store, order, registration, pricing, or product-related settings, not direct data theft.
Executive priority
Treat as a moderate-priority WordPress hygiene issue. Prioritize ecommerce sites because integrity changes to orders, pricing, checkout, registrations, or product presentation can create operational and revenue impact.
Technical view
CVE-2022-4888 is CWE-352 across multiple Addify plugins. CVSS 3.1 is 6.5, with network attack vector, low complexity, no attacker privileges, required user interaction, no confidentiality impact, high integrity impact, and no availability impact.
Likely exposure
WordPress or WooCommerce sites using one of the listed Addify plugins at affected versions are exposed. Exposure depends on installed plugin, version, and whether logged-in users with relevant permissions can be induced to trigger vulnerable actions.
Exploitation context
The bundle does not show CISA KEV listing or active exploitation. WPScan is tagged as an exploit/vulnerability database entry, but no source here proves exploitation in the wild. Successful abuse requires user interaction by a logged-in user.
Researcher notes
Evidence supports multiple CSRF flaws across named plugins, but does not enumerate every vulnerable action in this bundle. Avoid broad exploit assumptions; validate exposure by plugin version and by whether state-changing actions now enforce CSRF protections.
Mitigation direction
- Inventory all listed Addify plugins across WordPress sites.
- Update affected plugins to vendor-supported fixed versions where named.
- For plugins listed as affected through a version, check vendor guidance before assuming fixed status.
- Disable or remove plugins with no confirmed safe version if business risk is unacceptable.
- Reduce administrator browsing while logged into WordPress.
Validation and detection
- Confirm installed plugin names and versions against the CVE affected ranges.
- Verify fixed versions are deployed where the bundle names a fixed release.
- Review WordPress activity logs for unexpected settings, order, pricing, or product changes.
- Check staging code or vendor release notes for improved CSRF nonce checks.
- Confirm no affected plugin remains active without an accepted risk decision.
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-4888 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
- 6.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/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:L/PR:N/UI:R/S:U/C:N/I:H/A:N2.83.6Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
6.5MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://wpscan.com/vulnerability/2c2379d0-e373-4587-a747-429d7ee8f6ccCVE reference · exploit, vdb-entry
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.