CVE-2024-6559
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 Backup, Restore and Migrate WordPress Sites With the XCloner Plugin plugin for WordPress is vulnerable to Full Path Disclosure in all versions up to, and including, 4.7.3. This is due the plugin utilizing sabre without preventing direct access to the 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 XCloner WordPress plugin includes the sabre PHP library without proper access controls, allowing unauthenticated attackers to directly access library files that reveal the full server filesystem path. This information disclosure aids in reconnaissance for subsequent 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.
-
Identify if XCloner plugin is installedCheck the WordPress plugins directory (wp-content/plugins/) for the xcloner-backup-and-restore folder or similar XCloner plugin directoryAffected if The XCloner plugin directory exists on the WordPress installation
-
Locate the sabre library within the pluginSearch the XCloner plugin directory for folders or files containing 'sabre' in the name, typically found under vendor/ or lib/ subdirectoriesAffected if The sabre PHP library files are present within the XCloner plugin directory
-
Test direct web access to sabre library filesAttempt to access common sabre library entry points via HTTP request (such as files in the sabre/vobject, sabre/xml, or sabre/http directories) directly through the web browser without authenticationAffected if The sabre library files are served directly without requiring authentication or proper access controls
-
Check for path disclosure in sabre library responsesTrigger an error or request on sabre library files and inspect the response for server filesystem paths (such as /home/, /var/www/, or absolute paths)Affected if The server response reveals full filesystem paths when accessing sabre library files directly
-
Verify access control configurationReview .htaccess or web server configuration files in the sabre library directory to determine if direct access is explicitly blockedAffected if No .htaccess or access control rules exist to deny direct access to sabre library files
The environment is affected if XCloner plugin is installed with the sabre library and those library files can be accessed directly via web without authentication, allowing filesystem path disclosure.
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 dataBlock direct access to the sabre library files via .htaccess rules or web server configuration, or update to a patched version if available.
- 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-6559 — 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-6559 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