CVE-2024-6565
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 AForms — Form Builder for Price Calculator & Cost Estimation plugin for WordPress is vulnerable to Full Path Disclosure in all versions up to, and including, 2.2.6. This is due to the plugin utilizing the aura library and allowing direct access to the phpunit test files. 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 AForms WordPress plugin allows unauthenticated access to phpunit test files via the included aura library, which exposes the full server file path. This is a direct object reference vulnerability where test files that should not be web-accessible are reachable.
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.
-
Confirm AForms plugin is installedCheck the WordPress plugins directory for the AForms plugin folder, typically in wp-content/plugins/aforms or similar. Use wp-cli plugin list or inspect the plugin files directly.Affected if AForms plugin is present on the WordPress site
-
Identify the installed AForms versionRead the main plugin file (e.g., aforms.php) and locate the version header, or check the readme.txt file for the Version field.Affected if The installed version matches or falls within any affected version range listed for this CVE
-
Verify phpunit test files are web-accessibleAttempt to access common test file paths via HTTP: /wp-content/plugins/aforms/lib/aura/src/phpunit.xml and /wp-content/plugins/aforms/vendor/aura/aura/src/phpunit.xml or similar test file paths under the aura library.Affected if The test files return HTTP 200 and expose file contents rather than a 403/404 error
-
Check for exposed server file paths in responsesInspect the HTTP response body from any accessible phpunit test files for full server file paths (absolute paths like /var/www/html/ or C:\inetpub\).Affected if The response contains absolute server file paths indicating the vulnerability is active
A site is affected if AForms plugin is installed and its phpunit test files from the aura library are accessible over the web, exposing server file paths.
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 dataRestrict access to or remove the phpunit test files and associated aura library files from the web root, typically via .htaccess rules or server configuration to deny direct access to these paths.
- Consultation1.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA0.5 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-6565 — 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-6565 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