# CVE-2024-10486: Google for WooCommerce <= 2.8.6 - Information Disclosure via Publicly Accessible PHP Info File

> Unauthenticated attackers can access a public PHP info file to retrieve server and PHP configuration details, 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:** 18 Nov 2024
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-9hgq-6x66-3wfh

## What is CVE-2024-10486?

CVE-2024-10486 is a medium-severity vulnerability in Google for WooCommerce, published on 18 Nov 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2024-10486 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-10486 exists.

Public exploit code:

- Google for WooCommerce <= 2.8.6 - Information Disclosure via Publicly Accessible PHP Info File (nuclei): http/cves/2024/CVE-2024-10486.yaml

## Fix prompt for AI coding agents

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

What it is: CVE-2024-10486 is a medium-severity vulnerability in Google for WooCommerce, published on 18 Nov 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-10486 exists.

Affected product: Google for WooCommerce. 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-10486/ (Markdown: https://insights.sbomify.com/CVE-2024-10486/index.md)
```

## Sources

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

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