CVE-2024-9069 MEDIUM

CVE-2024-9069: Graphicsly – The ultimate graphics plugin for WordPress website builder ( Gutenberg, Elementor, Beaver Builder, WPBakery ) <= 1.0.2 - Authenticated (Author+) Stored Cross-Site Scripting via SVG File Upload

Vendor Besnikac
Product Graphicsly – The ultimate graphics plugin for WordPress website builder ( Gutenberg, Elementor, Beaver Builder, WPBakery )
Weakness CWE-79 · XSS
Published September 25, 2024
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 Graphicsly – The ultimate graphics plugin for WordPress website builder ( Gutenberg, Elementor, Beaver Builder, WPBakery ) plugin for WordPress is vulnerable to Stored Cross-Site Scripting via SVG File uploads in all versions up to, and including, 1.0.2 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Author-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses the SVG file.

Explanation of Vulnerability in Simple Terms

02Summary

The Graphicsly WordPress plugin versions 1.0.2 and earlier contain a stored cross-site scripting (XSS) vulnerability. An authenticated user with low privileges can inject malicious scripts that execute in the browsers of other site visitors, including administrators. The vulnerability affects the plugin's core functionality across multiple page builders (Gutenberg, Elementor, Beaver Builder, WPBakery).

What an attacker can do

03Attacker Capabilities

Inject malicious scripts that run in other users' browsers, potentially stealing credentials or performing actions as those users.

Potential impact on your site

04Site Impact

Any authenticated user can inject persistent malicious code affecting all site visitors, including admins. Requires immediate plugin update or deactivation.

Conditions required to exploit

05Prerequisites

Attacker must have a low-privilege WordPress account (e.g., contributor or subscriber role) and network access to the site.

Key dates

06Disclosure timeline

September 25, 2024 CVE published
April 8, 2026 Record updated

Related vulnerabilities

08Related CVE