dbcve.org
Getresponse FormsWordPress extension · Fatcatapps

CVE-2024-8740

MEDIUM · 6.1 CVSS v3.1 Published 2024-10-18
Fix available
A fix is available. Upgrade to after 2.5.6 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The GetResponse Forms by Optin Cat plugin for WordPress is vulnerable to Reflected Cross-Site Scripting due to the use of add_query_arg without appropriate escaping on the URL in all versions up to, and including, 2.5.7. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The GetResponse Forms by Optin Cat WordPress plugin (versions up to 2.5.7) is vulnerable to reflected Cross-Site Scripting (XSS) due to improper use of the WordPress add_query_arg() function without URL escaping. An attacker can craft a malicious URL containing JavaScript in the query parameters; when a user clicks this link, the script executes in their browser because the plugin outputs the unescaped URL parameter value.

MitigationUpdate the plugin to version 2.5.8 or later, which properly escapes the add_query_arg() output using esc_url() or esc_attr() before rendering in HTML.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Getresponse FormsWordPress extension
Affected:<= 2.5.6

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate the GetResponse Forms plugin
    In WordPress admin, go to Plugins > Installed Plugins and look for 'GetResponse Forms by Optin Cat' or 'Fatcatapps Getresponse Forms'. Note the plugin file path if accessible via FTP or file manager.
    Affected if The plugin is installed and active
  2. Identify the installed version
    In the Plugins list, find the version number displayed under the plugin name. Alternatively, check the plugin's main PHP file header (usually in /wp-content/plugins/getresponse-forms/ or similar path) for the 'Version' tag.
    Affected if The version number is 2.5.6 or lower
  3. Compare against affected range
    Compare your installed version to the affected range: versions 2.5.6 and below are vulnerable. Versions 2.5.7 and 2.5.8 may contain partial fixes but the advisory indicates 2.5.8 is the patched version.
    Affected if Installed version is 2.5.6 or lower
  4. Verify the vulnerability is exploitable
    Check if the plugin is actively configured or has published forms. The XSS triggers via URL query parameters when accessing plugin admin pages. No specific configuration check is needed; the flaw is in how the plugin handles URL parameters on any plugin-administered page.
    Affected if The plugin is active (even without forms configured, the reflected XSS vulnerability exists in the plugin code)

You are affected if the GetResponse Forms plugin is installed with version 2.5.6 or lower; upgrade to 2.5.8 or later to resolve.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 2.5.6
Interim mitigation

Update the plugin to version 2.5.8 or later, which properly escapes the add_query_arg() output using esc_url() or esc_attr() before rendering in HTML.

Recommended fix High confidence

Upgrade to GetResponse Forms version 2.5.8 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the 'GetResponse Forms by Optin Cat' plugin
  4. Check if an update is available and update to the latest version (2.5.8 or later)
  5. Alternatively, download the latest version from the WordPress Plugin Repository and upload via Plugins > Add New > Upload Plugin

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Getresponse Forms Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-8740 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-8740 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data