What this page helps you verify fast
This hub clusters tracked records for GetResponse for WordPress so operators can confirm whether a disclosed issue maps to the installed slug, version range, and patch path.
Review known vulnerability records for the WordPress plugin GetResponse for WordPress (`getresponse-integration`), including severity, CVE references, affected versions, and patch status.
Recent tracked CVEs on this page include CVE-2024-31104, CVE-2023-0167 and CVE-2022-35277, so operators can jump from disclosure to patch validation without scanning the full feed first.
Pair this plugin vulnerability hub with practical WordPress hardening, scanner, and patch workflow guidance.
Review patch cadence, privileged access, XML-RPC exposure, backups, and monitoring controls.
Use ownership, update testing, least privilege, and removal criteria to reduce plugin risk.
Compare scanner coverage for plugin CVEs, version detection, alert noise, and remediation workflow.
Use the hub as a decision layer before opening individual records: confirm whether the issue has a CVE, whether a fixed version exists, and whether the affected range overlaps production installs.
Affected range: Versions up to 5.5.19. Fixed version: 5.5.21.
Affected range: Versions up to 5.5.35. Fixed version is not listed yet.
Affected range: Versions up to 5.5.31. Fixed version: 5.5.32.
Start with the highest-signal CVE records for this WordPress plugin before scanning the full vulnerability feed.
| Tracked CVE | Issue Type | Affected Versions | Fixed Version | CVSS |
|---|---|---|---|---|
|
CVE-2022-35277
GetResponse <= 5.5.19 - Cross-Site Request Forgery
|
Cross-Site Request Forgery | Versions up to 5.5.19 | 5.5.21 | CVSS 8.8 |
|
CVE-2024-31104
GetResponse for WordPress <= 5.5.35 - Authenticated (Contributor+) Stored Cross-Site...
|
Stored Cross-Site Scripting | Versions up to 5.5.35 | No patch listed | CVSS 6.4 |
|
CVE-2023-0167
GetResponse for WordPress <= 5.5.31 - Authenticated (Contributor+) Stored Cross-Site...
|
Stored Cross-Site Scripting | Versions up to 5.5.31 | 5.5.32 | CVSS 6.4 |
GetResponse <= 5.5.19 - Cross-Site Request Forgery
GetResponse for WordPress <= 5.5.35 - Authenticated (Contributor+) Stored Cross-Site Scripting
GetResponse for WordPress <= 5.5.31 - Authenticated (Contributor+) Stored Cross-Site Scripting via Shortcode
This hub clusters tracked records for GetResponse for WordPress so operators can confirm whether a disclosed issue maps to the installed slug, version range, and patch path.
These recent records surface the CVE strings, patch cues, and direct report links most operators need first.
The GetResponse for WordPress plugin for WordPress is vulnerable to Stored Cross-Site Scripting in versions up to, and including, 5.5.35 due to insufficient input sanitization and output esc...
The GetResponse for WordPress plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's shortcode(s) in versions up to, and including, 5.5.31 due to insufficient inp...
The GetResponse plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 5.5.19. This is due to missing or incorrect nonce validation on one of its...
Sorted by latest disclosure date so newly published issues surface first.
The GetResponse for WordPress plugin for WordPress is vulnerable to Stored Cross-Site Scripting in versions up to, and including, 5.5.35 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with contributor-level access a...
The GetResponse for WordPress plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's shortcode(s) in versions up to, and including, 5.5.31 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible fo...
The GetResponse plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 5.5.19. This is due to missing or incorrect nonce validation on one of its functions. This makes it possible for unauthenticated attackers to trigger API Key updates...