dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2024-10486

MEDIUM · 5.3 CVSS v3.1 Published 2024-11-18
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 Google for WooCommerce plugin for WordPress is vulnerable to Information Disclosure in all versions up to, and including, 2.8.6. This is due to publicly accessible print_php_information.php file. This makes it possible for unauthenticated attackers to retrieve information about Webserver and PHP configuration, which can be used to aid other attacks.

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 Google for WooCommerce plugin for WordPress ships with a debug file (print_php_information.php) that is publicly accessible without authentication. This file outputs sensitive Webserver and PHP configuration details including version information, loaded extensions, paths, and environment variables, which can aid attackers in reconnaissance for more targeted exploits.

MitigationUpdate the Google for WooCommerce plugin to the latest version, or remove/disable the exposed print_php_information.php file and restrict access to any remaining debug files in production environments.

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 Google for WooCommerce plugin is installed
    Check WordPress plugins directory or admin panel for the Google for WooCommerce plugin presence and note the installed version
    Affected if The plugin is installed and the version is unpatched for this debug file exposure
  2. Locate the debug file in the plugin directory
    Search for print_php_information.php within the Google for WooCommerce plugin folder structure on the server filesystem
    Affected if The file exists in the plugin directory, indicating it was not removed from the installation
  3. Test public accessibility of the debug file
    Attempt to access the file via HTTP request (e.g., visit https://yourdomain.com/wp-content/plugins/google-listings-and-ads/print_php_information.php or similar path)
    Affected if The file returns an HTTP 200 response and displays PHP version, extensions, paths, or environment variables without authentication
  4. Verify the file exposes sensitive information
    Examine the output from the debug file - look for PHP version numbers, loaded extensions, server paths, or environment variable listings
    Affected if The file output contains sensitive system configuration details such as PHP version, loaded extensions, server paths, or environment variables that should not be publicly visible

A user is affected if the Google for WooCommerce plugin is installed with the print_php_information.php file present and publicly accessible without authentication, exposing server and PHP configuration details.

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

Update the Google for WooCommerce plugin to the latest version, or remove/disable the exposed print_php_information.php file and restrict access to any remaining debug files in production environments.

Recommended fix High confidence

2.8.7

  1. Update the Google for WooCommerce plugin to version 2.8.7 or later through the WordPress admin dashboard under Plugins > All Plugins
  2. Navigate to Plugins > All Plugins and check that the Google for WooCommerce plugin shows version 2.8.7 or higher
  3. Verify the vulnerability is remediated by confirming the print_php_information.php file is no longer publicly accessible or has been removed

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-10486 — 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-10486 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