CVE•Published 2024-07-18•Modified 2026-04-08•1 article on news•6 live references•NVD data

CVE-2024-3242Brizy · Brizy

Vulnerability data via NVD (ingested)

CVSS v3.1

8.8

HIGH

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

EPSS percentile

—

Weaknesses (CWE)

CWE-434Unrestricted Upload of File with Dangerous Type

Description

The Brizy – Page Builder plugin for WordPress is vulnerable to arbitrary file uploads due to missing file extension validation in the validateImageContent function called via storeImages in all versions up to, and including, 2.4.43. This makes it possible for authenticated attackers, with contributor access and above, to upload arbitrary files on the affected site's server which may make remote code execution possible. Version 2.4.44 prevents the upload of files ending in .sh and .php. Version 2.4.45 fully patches the issue.

Timeline

Published 2024-07-18

Modified 2026-04-08

External references

NVD MITRE Exploit-DB GitHub PoC trickest/cve VulnCheck

Search for exposed instances

Shodan + Censys queries derived from NVD's CPE data. The vuln tag catches assets Shodan has explicitly linked to this CVE; the product / banner fingerprints find exposed instances even when the vuln tag was never applied (which is common).

Shodan · vuln tag0 hosts

vuln:CVE-2024-3242

Hosts Shodan has explicitly fingerprinted as vulnerable.

Shodan · WP plugin path

http.html:"/wp-content/plugins/brizy/"

Matches any site loading the "brizy" plugin — doesn't rely on Shodan's vuln tag.

Shodan · product

product:"Brizy Brizy"

All exposed Brizy Brizy instances — cross-reference with the CVE's affected-version range.

Shodan · banner/body mention

http.html:"Brizy"

HTTP body or banner mentions "Brizy" — catches deploys Shodan didn't identify as a product.