CVE-2024-6573
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 Intelligence plugin for WordPress is vulnerable to Full Path Disclosure in all versions up to, and including, 1.4.0. This is due the plugin not preventing direct access to the /vendor/levelten/intel/realtime/index.php file and display_errors being enabled. 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 Intelligence WordPress plugin fails to restrict direct access to /vendor/levelten/intel/realtime/index.php. When display_errors is enabled in PHP, accessing this file causes the server to reveal the full filesystem path in error messages, enabling attackers to gather reconnaissance information for targeted 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.
-
Check if Intelligence plugin is installedList wp-content/plugins/ directory or check via WordPress admin panel for the Intelligence pluginAffected if The Intelligence plugin by Level Ten is present in the WordPress installation
-
Locate the vulnerable fileCheck for existence of /vendor/levelten/intel/realtime/index.php within the plugin directoryAffected if The file wp-content/plugins/intelligence/vendor/levelten/intel/realtime/index.php exists
-
Verify PHP display_errors is enabledCheck php.ini for display_errors = On, or create a PHP info page to inspect the runtime configurationAffected if display_errors is set to On in PHP configuration
-
Test direct access to vendor pathAttempt to access the URL /wp-content/plugins/intelligence/vendor/levelten/intel/realtime/index.php directly via HTTP requestAffected if The server responds and reveals full filesystem path in error messages (requires display_errors=On)
-
Check .htaccess protection on vendor directoryExamine .htaccess files in the plugin or vendor directories for rules blocking direct access to /vendor/Affected if No .htaccess rules exist to deny direct access to the vendor directory
The environment is affected if the Intelligence plugin is installed, the vulnerable PHP file exists, display_errors is enabled, and no access restrictions block direct requests to the vendor directory.
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 dataDisable display_errors in php.ini or add .htaccess rules to prevent direct access to the vendor directory.
- Consultation1.0 h
- Implementation1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-6573 — 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-6573 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