Security readout for executives and security teams
Plain-English summary
This is a medium-severity CSRF issue in the GetResponse for WordPress plugin affecting versions 5.5.20 and earlier. A successful attack could trick a logged-in site user into changing plugin-related data, with Patchstack’s title specifically referencing API key update impact.
Executive priority
Treat this as a targeted WordPress plugin configuration risk, not an enterprise-wide emergency. Prioritize sites using GetResponse for marketing or customer communications because unauthorized API key changes could disrupt integrations or expose limited data paths.
Technical view
CVE-2022-35277 is CWE-352 in GetResponse for WordPress <=5.5.20. The CVSS 3.1 vector is AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N, meaning remote reachability, low complexity, no attacker privileges, required user interaction, and limited confidentiality/integrity impact.
Likely exposure
Exposure is limited to WordPress sites that have the GetResponse integration plugin installed at version 5.5.20 or earlier. Sites without this plugin are not indicated as affected by the supplied sources.
Exploitation context
The provided bundle does not show CISA KEV listing or active exploitation evidence. The CVSS vector indicates exploitation requires user interaction, consistent with CSRF, but no exploit details should be assumed from the supplied evidence.
Researcher notes
Evidence is sparse in the supplied bundle. The Patchstack reference title indicates CSRF leading to API key update, but the bundle does not include full vulnerable endpoint detail, fixed version detail, exploit activity, or proof-of-concept status.
Mitigation direction
- Inventory WordPress sites for the GetResponse integration plugin and installed version.
- Check vendor and WordPress plugin guidance for the fixed or current supported release.
- Update affected plugin installations when vendor guidance confirms a safe version.
- Review GetResponse API key settings and restore trusted values if changed unexpectedly.
- Temporarily disable the plugin if no remediation path is available and risk is unacceptable.
Validation and detection
- Confirm whether each WordPress site uses GetResponse for WordPress version 5.5.20 or earlier.
- Review plugin settings for unexpected GetResponse API key changes.
- Check WordPress administrative logs for suspicious configuration changes around user sessions.
- Verify remediation against vendor or WordPress plugin release guidance before closing.
- Document whether the plugin is absent, updated, disabled, or still exposed.
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-35277 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:L/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:L/I:L/A:N2.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:L/I:L/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://patchstack.com/database/vulnerability/getresponse-integration/wordpress-getresponse-plugin-5-5-18-cross-site-request-forgery-csrf-vulnerability-leading-to-api-key-update/_s_id=cveCVE reference · x_refsource_CONFIRM
- https://wordpress.org/plugins/getresponse-integration/CVE 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.
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.