dbcve.org
Information ExposureWeakness · CWE-200

CVE-2024-6574

MEDIUM · 5.3 CVSS v3.1 Published 2024-07-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
The Laposta plugin for WordPress is vulnerable to Full Path Disclosure in all versions up to, and including, 1.12. This is due to the plugin not preventing direct access to several 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. This plugin is no longer being maintained and has been closed for downloads.

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 confidence

The Laposta WordPress plugin (versions up to 1.12) fails to prevent direct access to test files, allowing unauthenticated attackers to retrieve the full server path via the web root. This information disclosure aids in reconnaissance but requires another vulnerability to cause actual damage.

MitigationRemove the plugin if unused; otherwise locate and delete or protect the test files via .htaccess rules to block direct access, and disable PHP error display server-wide.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Laposta plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Laposta' or checkwp-content/plugins/ directory for a laposta folder
    Affected if The Laposta plugin is present on the WordPress site
  2. Check installed version
    In WordPress admin_plugins list, view the Laposta plugin details to see the version number, or read the main plugin file header in wp-content/plugins/laposta/
    Affected if Version is 1.12 or lower (any version up to and including 1.12)
  3. Locate test files in plugin directory
    Browse the wp-content/plugins/laposta/ directory for any files with 'test' or 'example' in the name, or files in a test/example subdirectory
    Affected if Test or example files exist within the plugin directory
  4. Verify test files are web-accessible
    Attempt to access suspected test files directly via HTTP (e.g., curl or browser request to /wp-content/plugins/laposta/test*.php)
    Affected if The test files return a valid HTTP response rather than 404 or 403
  5. Confirm path disclosure behavior
    Examine the response from accessing any accessible test files for server path strings (e.g., /home/, /var/www/, C:\)
    Affected if The test file output contains absolute server file paths

You are affected if the Laposta plugin version is 1.12 or lower AND test files are directly accessible via the web and reveal server paths.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Remove the plugin if unused; otherwise locate and delete or protect the test files via .htaccess rules to block direct access, and disable PHP error display server-wide.

Recommended fix Moderate confidence
  1. Uninstall and completely remove the Laposta plugin from the WordPress installation, as the plugin is no longer maintained and no longer available for download.
  2. If the plugin cannot be immediately removed, configure the web server (Apache/Nginx) to deny direct access to any test files within the plugin directory using .htaccess rules or server configuration blocks.
  3. Audit the WordPress installation for any other abandoned plugins and remove them to reduce the attack surface.

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-6574 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-6574 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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