Security readout for executives and security teams
Plain-English summary
This CVE affects a WordPress Stripe donation/payment plugin. A malicious site could potentially trick a legitimate WordPress user into causing an unintended change in the plugin. The reported impact is limited to integrity, not data theft or outage, but payment-related plugins deserve prompt review because configuration mistakes can affect donations or transactions.
Executive priority
Treat as a moderate-priority WordPress exposure. It is not documented as actively exploited, but it affects a payment-adjacent plugin and may allow unauthorized changes if a trusted user is tricked. Confirm exposure first, then remediate or disable affected installations.
Technical view
CVE-2022-47422 is a CSRF issue in HM Plugin Accept Stripe Donation – AidWP, reported for versions up to 3.1.5. The CVSS 3.1 vector is AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N. The sources do not describe the exact vulnerable action, endpoint, patch version, or proof of exploitation.
Likely exposure
Exposure is likely limited to WordPress sites with the wp-stripe-donation / Accept Stripe Donation – AidWP plugin installed at version 3.1.5 or earlier. The source bundle does not provide CPEs or a complete version matrix, so plugin inventory is required.
Exploitation context
The CVE is not listed as KEV in the provided bundle, and no cited source states active exploitation. Exploitation requires user interaction, consistent with CSRF, where an attacker relies on a victim’s browser session rather than attacker authentication.
Researcher notes
Evidence is sparse. The bundle identifies CWE-352, plugin slug wp-stripe-donation, affected versions up to 3.1.5, and CVSS 4.3. It does not name endpoints, affected actions, exploit maturity, or a fixed version. Avoid assuming confidentiality or availability impact.
Mitigation direction
- Inventory WordPress sites for the wp-stripe-donation plugin and installed version.
- Check vendor and Patchstack guidance for a fixed release or official remediation.
- Upgrade if a fixed version is available from trusted WordPress or vendor channels.
- Temporarily disable the plugin where business impact permits until remediation is confirmed.
- Limit WordPress admin access and review privileged accounts for least privilege.
Validation and detection
- Confirm whether Accept Stripe Donation – AidWP is installed on each WordPress property.
- Record plugin versions and prioritize any installation at 3.1.5 or earlier.
- Check Patchstack and CVE records for updated remediation or affected-version details.
- Review WordPress audit logs for unexpected plugin or payment configuration changes.
- Verify administrative plugin actions use anti-CSRF protections such as nonces.
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-47422 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
- 4.3 (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: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:L/A:N2.81.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
4.3MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
Source materials
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.