Skip to content
Fencer Intel
medium 5.4

CVE-2024-30453 json

WordPress Brave plugin <= 0.6.5 - Server Side Request Forgery (SSRF) vulnerability

published 2y ago modified 4mo ago also BIT-wordpress-2024-30453 , BIT-wordpress-multisite-2024-30453 , EUVD-2024-28374

cvss
5.4
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 23%
public exploits
0
none known

Summary

Server-Side Request Forgery (SSRF) vulnerability in Brave Brave Popup Builder.This issue affects Brave Popup Builder: from n/a through 0.6.5.

Patch / fix

  • bitnami wordpress 0.6.6
  • bitnami wordpress-multisite 0.6.6
  • Brave Brave Popup Builder 0.6.6

Is CVE-2024-30453 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
2y ago

Exploit prediction

0.31% chance of exploitation in the next 30 days, higher than 23% of all scored CVEs (FIRST EPSS, 2026-11-11).

CVSS scores

assigned by version score vector
CNA 3.1 5.4 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N
OSV 3.1 5.4 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N

Affected packages

ecosystem package affected fixed in
bitnami wordpress
<0.6.6
0.6.6
bitnami wordpress-multisite
<0.6.6
0.6.6

Affected products

  • Brave Brave Popup Builder

Classification

Weakness
  • CWE-918 Server-Side Request Forgery
Technology feeds

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.