CVE-2024-6550 json
Gravity Forms: Multiple Form Instances <= 1.1.1 - Unauthenticated Full Path Disclosure
published 2y ago modified 4mo ago also EUVD-2024-47623
- cvss
- 5.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 39%
- public exploits
- 0
- none known
Summary
The Gravity Forms: Multiple Form Instances plugin for WordPress is vulnerable to Full Path Disclosure in all versions up to, and including, 1.1.1. This is due to the plugin leaving test files with display_errors on. This makes it possible for unauthenticated attackers to retrieve the full path of the web application, which can be used to aid other attacks. The information displayed is not useful on its own, and requires another vulnerability to be present for damage to an affected website.
Is CVE-2024-6550 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
- partial
- Assessed
- 2y ago
Exploit prediction
0.45% chance of exploitation in the next 30 days, higher than 39% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N |
Affected products
- tyxla Gravity Forms: Multiple Form Instances
- nikunj gravity_forms_multiple_form_instances
Classification
- Weakness
-
- CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/3ec761eb-6bd9-4c19-a98d-cb4738922a84?source=cve
- plugins.trac.wordpress.org /browser/gravity-forms-multiple-form-instances/trunk/tests/bootstrap.php
- plugins.trac.wordpress.org /changeset?sfp_email=&sfph_mail=&reponame=&old=3114842%40gravity-forms-multiple-form-instances&new=3114842%40g
Sources
- CVE List CVE-2024-6550
- NVD CVE-2024-6550
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.