CVE-2024-6550
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Gravity Forms: Multiple Form Instances WordPress plugin (versions up to 1.1.1) contains test files with PHP's display_errors setting enabled, allowing unauthenticated attackers to trigger these files and obtain the full server filesystem path. This information disclosure is low severity on its own but can aid in reconnaissance for more severe attacks.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify the plugin is installedCheck the WordPress plugins directory for the 'gravity-forms-multiple-form-instances' folder, or look for the plugin in the WordPress admin under Plugins > Installed PluginsAffected if The plugin folder exists in wp-content/plugins/
-
Check the installed versionLook in the plugin's main PHP file (usually gravity-forms-multiple-form-instances.php) for the 'Version' header in the plugin comment block, or check via WordPress admin plugin listAffected if Version is 1.1.1 or lower (any version up to and including 1.1.1)
-
Locate test files in the plugin directoryBrowse the plugin directory (wp-content/plugins/gravity-forms-multiple-form-instances/) for any files in a 'test' or 'tests' subfolder, or files named with 'test' or 'debug' in the filenameAffected if Test files exist in the plugin folder
-
Inspect PHP display_errors setting in test filesOpen any found test files and look for a line containing 'ini_set' or 'display_errors' - check if display_errors is set to On or 1, or if the setting is missing (defaulting to On)Affected if display_errors is explicitly set to On/1, or the file contains an ini_set call enabling error display
A user is affected if they have the plugin installed at version 1.1.1 or lower AND test files exist in the plugin directory with display_errors enabled, exposing filesystem paths to unauthenticated visitors.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataRemove or disable the test files in the plugin directory, or ensure PHP display_errors is set to Off in the plugin's test files. Alternatively, update the plugin to the latest version if a patched release is available.
- Consultation1.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-6550 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-6550 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data