CVE-2025-14984 MEDIUM

CVE-2025-14984: Gutenverse Form <= 2.3.2 - Authenticated (Author+) Stored Cross-Site Scripting via SVG File Upload

Vendor Jegstudio
Product Gutenverse Form – Contact Form Builder, Booking, Reservation, Subscribe for Block Editor
Weakness CWE-79 · XSS
Published January 8, 2026
Last update April 8, 2026

CVSS base score

6.4/10
Attack vector Network
Attack complexity Low
Privileges required Low
User interaction None
Confidentiality Low
Integrity Low

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N

What the vulnerability does

01Description

The Gutenverse Form plugin for WordPress is vulnerable to Stored Cross-Site Scripting via SVG file upload in all versions up to, and including, 2.3.2. This is due to the plugin's framework component adding SVG to the allowed MIME types via the upload_mimes filter without implementing any sanitization of SVG file contents. This makes it possible for authenticated attackers, with Author-level access and above, to upload SVG files containing malicious JavaScript that executes when the file is viewed, leading to arbitrary JavaScript execution in victims' browsers.

Explanation of Vulnerability in Simple Terms

02Summary

Gutenverse Form versions up to 2.3.2 contain a cross-site scripting vulnerability that allows authenticated users to inject malicious scripts. The vulnerability affects the form builder interface and can impact other users viewing or interacting with affected forms. Site administrators should update to a version newer than 2.3.2 to remediate this issue.

What an attacker can do

03Attacker Capabilities

Inject malicious scripts that execute in other users' browsers when they view or interact with forms.

Potential impact on your site

04Site Impact

Authenticated attackers can inject scripts affecting other site users, potentially stealing credentials or session tokens.

Conditions required to exploit

05Prerequisites

Attacker must have a WordPress user account with low privileges (e.g., subscriber or contributor role).

Key dates

06Disclosure timeline

January 8, 2026 CVE published
April 8, 2026 Record updated

Related vulnerabilities

08Related CVE