other

The Gravity Forms WordPress Plugin Supply Chain Attack

Updated 18 Nov 2026 · Incident date 9 Jul 2025

Gravity Forms 2.9.11.1 and 2.9.12 manual installers from gravityforms.com carried a backdoor that ran code sent by strangers in July 2025.

The fixed version is 2.9.13. Only manual downloads and Composer installs were affected, according to SecurityWeek.

What happened

Attackers added malicious code to the plugin package that the official site served.

  • The code sat in gravityforms/common.php and includes/settings/class-settings.php.
  • It sent site data to the attacker, including the site URL, WordPress and PHP versions, active plugins and user count.
  • It downloaded a Base64-encoded PHP file and wrote it to disk, for example wp-includes/bookmark-canonical.php.
  • A second backdoor accepted requests with a secret token. An attacker can use it to create administrator accounts, run PHP code and upload files.
  • The code also blocked update attempts.

People downloaded the bad plugin on 9 and 10 July 2025. RocketGenius released 2.9.13 on 11 July.

Affected versions

  • Gravity Forms 2.9.11.1 and 2.9.12, downloaded manually from gravityforms.com on 9 and 10 July 2025.
  • Composer installs made from the official site during the same window. BleepingComputer states that a Composer install of 2.9.11 on 10 to 11 July was affected. SecurityWeek says 2.9.11.1.
  • Fixed in 2.9.13.
  • Installs from the WordPress.org repository were not affected, according to Patchstack.

Indicators of compromise

  • Domains: gravityapi.org and gravityapi.io.
  • IP addresses: 185.193.89.19 and 193.160.101.6.
  • Files: wp-includes/bookmark-canonical.php and wp-includes/block-caching.php.
  • A reference to gravityapi.org in gravityforms/common.php.
  • A list_sections function in includes/settings/class-settings.php.
  • Administrator accounts that nobody on your team created.

How to check

Search the plugin folder and wp-includes for the domain and the dropped files. Run this in the WordPress root.

grep -rIl "gravityapi" wp-content/plugins/gravityforms; ls -l wp-includes/bookmark-canonical.php wp-includes/block-caching.php

Read the version from the plugin file. A version of 2.9.13 or later does not prove a clean site.

grep -i -m 1 'Version:' wp-content/plugins/gravityforms/gravityforms.php

What to do now

  1. Update Gravity Forms to 2.9.13 or later from a trusted source.
  2. Delete the dropped files in wp-includes if they exist, and remove administrator accounts that you do not recognize.
  3. Change all administrator, database and hosting passwords. Rotate the WordPress salts.
  4. If you find the backdoor, restore the site from a backup made before 9 July 2025 or rebuild it.

Frequently asked questions

Which Gravity Forms versions were compromised?

Versions 2.9.11.1 and 2.9.12 from the official gravityforms.com download page. Version 2.9.13 removed the malicious code.

Did the Gravity Forms attack affect automatic updates?

No. SecurityWeek reports that the auto-update mechanism and the Gravity API service were not compromised.

Sources

  1. patchstack.com/articles/critical-malware-found-in-gravityforms-official-plugin-site/
  2. bleepingcomputer.com/news/security/wordpress-gravity-forms-developer-hacked-to-push-backdoored-plugins/
  3. securityweek.com/hackers-inject-malware-into-gravity-forms-wordpress-plugin/

Send this page to the person who looks after AI at your company.

Email it

More supply chain attacks

All 172 attacks in the library · What is a supply chain attack? · How to prevent supply chain attacks

Check the next update before you install it

Vigilance compares the version you trust with the new one. It names the one file that gained a power the old version did not have.

Start the free 14-day trialBrowse the attack library