Gravity Forms WebhooksWordPress extension · Rocketgenius
CVE-2024-13845
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 · uneditedThe Gravity Forms WebHooks plugin for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 1.6.0 via the 'process_feed' method of the GF_Webhooks class This makes it possible for authenticated attackers, with Administrator-level access and above, to make web requests to arbitrary locations originating from the web application and can be used to query and modify information from internal services.
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 confidenceThe Gravity Forms WebHooks plugin for WordPress contains an SSRF vulnerability in the process_feed method of the GF_Webhooks class. Authenticated administrators can abuse this to make arbitrary web requests from the server, potentially accessing internal services or exfiltrating data.
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
Gravity Forms WebhooksWordPress extension
< 1.7.0CVSS 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
- High
- User interaction
- None
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/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 checksWork through these to decide whether this CVE applies to you.
-
Verify Gravity Forms WebHooks plugin is installedNavigate to WordPress admin > Plugins or inspect wp-content/plugins/ directory for 'gravityforms-webhooks' or 'gravity-forms-webhooks' folderAffected if Plugin folder exists in the WordPress installation
-
Check installed plugin versionIn WordPress admin > Plugins, find the Gravity Forms WebHooks entry and compare the version number against 1.7.0. Alternatively, read the main plugin PHP file and look for the 'Version' header in the plugin comments.Affected if Version listed is below 1.7.0 (e.g., 1.6, 1.5, etc.)
-
Confirm WebHooks feed is configuredNavigate to Forms > Settings > WebHooks in the WordPress admin panel, or inspect the wp_gf_addon_feed database table for entries with feed_type or addon_slug containing 'webhook'Affected if One or more WebHook feeds are active or configured with a URL target
-
Check for suspicious outbound requestsReview server access logs and WordPress debug logs for unusual outbound HTTP requests originating from the WordPress server, particularly to internal/private IP ranges or local network endpointsAffected if Unexpected outbound requests to internal services are present in logs around the time of webhook configuration changes
The environment is affected if the Gravity Forms WebHooks plugin version is below 1.7.0 and at least one WebHook feed is configured and active.
Generated from the published advisory. Verify against your own configuration.
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 · scoped1.7.0
Update the Gravity Forms WebHooks plugin to version 1.6.1 or later, which contains proper validation of webhook URLs to prevent SSRF attacks.
Gravity Forms Webhooks version 1.7.0
- Backup your WordPress site before making any changes
- Navigate to the WordPress admin dashboard
- Go to Plugins > Installed Plugins
- Locate the Gravity Forms Webhooks plugin
- Update the plugin to version 1.7.0 or later
- Verify the update was successful by checking the plugin version
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Gravity Forms Webhooks
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-13845 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-13845 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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