CVE-2024-7389 json
Forminator <= 1.29.1 - HubSpot Developer API Key Sensitive Information Exposure
published 2y ago modified 4mo ago also EUVD-2024-48325
- cvss
- 7.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.7%
- EPSS 0.7% chance of exploitation in 30 days, percentile 51%
- public exploits
- 0
- none known
Summary
The Forminator plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 1.29.1 via class-forminator-addon-hubspot-wp-api.php. This makes it possible for unauthenticated attackers to extract the HubSpot integration developer API key and make unauthorized changes to the plugin's HubSpot integration or expose personally identifiable information from plugin users using the HubSpot integration.
Patch / fix
- incsub forminator 1.29.2
Is CVE-2024-7389 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- total
- Assessed
- 2y ago
Exploit prediction
0.66% chance of exploitation in the next 30 days, higher than 51% of all scored CVEs (FIRST EPSS, 2026-11-11).
Exploits and checks
- vicarius.io https://www.vicarius.io/vsociety/posts/source-code-dive-to-hunt-for-secrets-in-forminator-code-cve-2024-7389 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
Affected products
- wpmudev Forminator Forms – Contact Form, Payment Form & Custom Form Builder
- incsub forminator
Classification
- Weakness
-
- CWE-522 Insufficiently Protected Credentials
- Technology feeds
References
-
plugins.trac.wordpress.org
/changeset/3047085/forminator/trunk/addons/pro/hubspot/lib/class-forminator-addon-hubspot-wp-api.php
patch
-
vicarius.io
/vsociety/posts/source-code-dive-to-hunt-for-secrets-in-forminator-code-cve-2024-7389
exploit, third-party-advisory
-
wordfence.com
/threat-intel/vulnerabilities/id/0d04b822-a48a-485e-b9b5-f5a213307c71?source=cve
third-party-advisory
-
developers.hubspot.com
/docs/api/webhooks#scopes
related
-
developers.hubspot.com
/docs/api/webhooks#manage-settings-via-api
related
Sources
- CVE List CVE-2024-7389
- NVD CVE-2024-7389
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.