CVE-2024-6557
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 SchedulePress – Auto Post & Publish, Auto Social Share, Schedule Posts with Editorial Calendar & Missed Schedule Post Publisher plugin for WordPress is vulnerable to Full Path Disclosure in all versions up to, and including, 5.1.3. This is due the plugin utilizing the wpdeveloper library and leaving the demo files in place 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 SchedulePress plugin uses the wpdeveloper library which ships with demo files that remain accessible on the server. When PHP's display_errors setting is enabled, these demo files output PHP error messages that expose the full absolute file system path of the WordPress installation, allowing unauthenticated attackers to discover internal server paths.
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 SchedulePress plugin versionIn WordPress admin, go to Plugins > Installed Plugins > SchedulePress and note the version number. Alternatively, inspect the main plugin file (schedulepress.php) and look for the 'Version:' header comment.Affected if The installed version is lower than 5.1.4
-
Locate wpdeveloper library demo filesBrowse the plugin directory (wp-content/plugins/schedulepress/) for a wpdeveloper folder or similar library directory. Look for files with names containing 'demo', 'sample', or 'test' in that directory.Affected if Demo, sample, or test files from the wpdeveloper library are present in the plugin directory
-
Verify PHP display_errors settingCheck your PHP configuration by creating a phpinfo() file or consulting your php.ini. Look for the display_errors directive. You can also check .htaccess for php_value display_errors settings.Affected if PHP display_errors is set to On (enabled)
-
Test demo file accessibility via HTTPAttempt to access suspected demo file URLs on your server (for example: /wp-content/plugins/schedulepress/includes/wpdeveloper/demo.php or similar paths). Request the file directly through a web browser or curl.Affected if The demo file is accessible via web request and returns any output
You are affected if SchedulePress version is below 5.1.4 AND demo files exist AND PHP display_errors is enabled, as this combination allows 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 dataDisable PHP's display_errors setting in php.ini or .htaccess, and remove any remaining demo files from the wpdeveloper library. Update to plugin version 5.1.4 or later if 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-6557 — 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-6557 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