<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Gravity-Forms on Aretiq AI</title><link>https://aretiq.ai/tags/gravity-forms/</link><description>Recent content in Gravity-Forms on Aretiq AI</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 01 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://aretiq.ai/tags/gravity-forms/index.xml" rel="self" type="application/rss+xml"/><item><title>CVE-2026-48866 — WordPress Gravity Forms Plugin File Upload Path Traversal Arbitrary File Deletion</title><link>https://aretiq.ai/research/vul260601-cve-2026-48866-wordpress-gravity-forms-plugin-file-upload-path-traversal-arbitrary-file-deletion/</link><pubDate>Mon, 01 Jun 2026 00:00:00 +0000</pubDate><guid>https://aretiq.ai/research/vul260601-cve-2026-48866-wordpress-gravity-forms-plugin-file-upload-path-traversal-arbitrary-file-deletion/</guid><description>&lt;h2 id="1-overview">1. Overview&lt;/h2>
&lt;p>A path traversal vulnerability exists in the Gravity Forms WordPress plugin&amp;rsquo;s file deletion mechanism. When processing entries that contain file upload fields, the plugin converts stored file URLs to filesystem paths using a simple string replacement without validating that the resulting path remains within the uploads directory. An unauthenticated attacker can submit a form with a crafted &lt;code>gform_uploaded_files&lt;/code> parameter containing directory traversal sequences (&lt;code>../&lt;/code>), which are stored in the entry database. When a privileged user subsequently deletes the entry or its attached files, the traversal sequences cause the plugin to delete arbitrary files on the server. Deleting critical files such as &lt;code>wp-config.php&lt;/code> results in complete site unavailability. Rocketgenius addressed this vulnerability in Gravity Forms version 2.10.1.&lt;/p></description></item></channel></rss>