# CVE-2024-6557: SchedulePress <= 5.1.3 - Unauthenticated Full Path Disclosure

> Unauthenticated attackers can retrieve the full web application path via exposed demo files, aiding further attacks.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Jul 2024
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-579q-534h-hjh5

## What is CVE-2024-6557?

CVE-2024-6557 is a medium-severity vulnerability in wpdevteam SchedulePress – Auto Post & Publish, Auto Social Share, Schedule Posts with Editorial Calendar & Missed Schedule Post Publisher, published on 16 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The 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.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2024-6557?


## How do I fix CVE-2024-6557?

No fix has been published for CVE-2024-6557 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-6557 being exploited?

There is no known exploitation of CVE-2024-6557 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-6557 and fix it if it is affected.

What it is: CVE-2024-6557 is a medium-severity vulnerability in wpdevteam SchedulePress – Auto Post & Publish, Auto Social Share, Schedule Posts with Editorial Calendar & Missed Schedule Post Publisher, published on 16 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-6557 in the wild and no public exploit code.

Affected product: wpdevteam SchedulePress – Auto Post & Publish, Auto Social Share, Schedule Posts with Editorial Calendar & Missed Schedule Post Publisher. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-6557/ (Markdown: https://insights.sbomify.com/CVE-2024-6557/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-6557
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-6557
- OSV: https://osv.dev/vulnerability/CVE-2024-6557

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-6557/
Summaries are generated and may contain mistakes; the official description above is the record.