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.phpandincludes/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.organdgravityapi.io. - IP addresses:
185.193.89.19and193.160.101.6. - Files:
wp-includes/bookmark-canonical.phpandwp-includes/block-caching.php. - A reference to
gravityapi.orgingravityforms/common.php. - A
list_sectionsfunction inincludes/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
- Update Gravity Forms to 2.9.13 or later from a trusted source.
- Delete the dropped files in
wp-includesif they exist, and remove administrator accounts that you do not recognize. - Change all administrator, database and hosting passwords. Rotate the WordPress salts.
- 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
Send this page to the person who looks after AI at your company.