dbcve.org
Information ExposureWeakness · CWE-200

CVE-2025-6082

MEDIUM · 5.3 CVSS v3.1 Published 2025-07-22
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 Birth Chart Compatibility plugin for WordPress is vulnerable to Full Path Disclosure in all versions up to, and including, 2.0. This is due to insufficient protection against directly accessing the plugin's index.php file, which causes an error exposing the full path. 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 confidence

The Birth Chart Compatibility WordPress plugin (versions up to 2.0) contains a Full Path Disclosure vulnerability where directly accessing the plugin's index.php file triggers a PHP error that exposes the full server filesystem path. This occurs due to missing access control (typically a `defined('ABSPATH')` check) at the beginning of the file, allowing unauthenticated attackers to obtain sensitive path information.

MitigationAdd a WordPress access control guard (e.g., `defined('ABSPATH') || exit;`) at the top of the plugin's index.php file to prevent direct execution. Alternatively, remove or rename the index.php file if not required for plugin functionality.

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. Locate the plugin installation directory
    Check your WordPress plugins folder (typically wp-content/plugins/) for a directory named 'birth-chart-compatibility' or similar variant. Verify the exact folder name used by the plugin.
    Affected if The plugin directory exists in the WordPress plugins folder
  2. Identify the installed plugin version
    Open the main plugin file (usually birth-chart-compatibility.php or similar) and look for the version declaration in the plugin header comment, or check readme.txt for the Version field. Compare against version 2.0 or lower.
    Affected if Installed version is 2.0 or lower (including unversioned releases)
  3. Verify the index.php file exists
    Check the plugin directory for an index.php file. This file is the entry point that can be directly accessed and triggers the path disclosure.
    Affected if The index.php file exists within the plugin directory
  4. Inspect index.php for ABSPATH access guard
    Open the plugin's index.php file and examine the first few lines (within the first 5 lines). Look for a line containing 'defined(' and 'ABSPATH' (e.g., 'defined(ABSPATH) || exit;'). If this guard is missing, the file is vulnerable.
    Affected if The ABSPATH guard is absent from the beginning of index.php (no 'defined(ABSPATH)' check present)
  5. Test for path disclosure (optional manual verification)
    If you have CLI access, attempt to execute the index.php file directly via PHP from the web server context or simulate a direct request. A vulnerable file will output a PHP error message containing the full server filesystem path.
    Affected if Direct access produces a PHP error revealing the full server path

You are affected if the Birth Chart Compatibility plugin (version 2.0 or lower) is installed AND the index.php file lacks the defined('ABSPATH') guard, allowing full path disclosure when accessed directly.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Add a WordPress access control guard (e.g., `defined('ABSPATH') || exit;`) at the top of the plugin's index.php file to prevent direct execution. Alternatively, remove or rename the index.php file if not required for plugin functionality.

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

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

Check whether your project pulls in CVE-2025-6082 — 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-2025-6082 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