How severe is GHSA-cgwq-6prq-8h9q?

GHSA-cgwq-6prq-8h9q has a CVSS score of 5.4/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-cgwq-6prq-8h9q?

GHSA-cgwq-6prq-8h9q affects the following packages: microsoft/microsoft-graph (Packagist), microsoft/microsoft-graph (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-cgwq-6prq-8h9q?

Update microsoft/microsoft-graph to 1.109.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-cgwq-6prq-8h9q is resolved across your whole dependency graph.

How do I detect GHSA-cgwq-6prq-8h9q in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for microsoft/microsoft-graph. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-cgwq-6prq-8h9q if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-cgwq-6prq-8h9q?

O3 pinpoints whether GHSA-cgwq-6prq-8h9q is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-cgwq-6prq-8h9q actively exploited in the wild?

No public exploit code has been indexed for GHSA-cgwq-6prq-8h9q yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-cgwq-6prq-8h9q?

GHSA-cgwq-6prq-8h9q has an EPSS (Exploit Prediction Scoring System) score of 2.2%, placing it in the 80th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-cgwq-6prq-8h9q?

GHSA-cgwq-6prq-8h9q is classified as Information Exposure (CWE-200). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-cgwq-6prq-8h9q published, and has it been updated?

GHSA-cgwq-6prq-8h9q was published on December 5, 2023 and was last updated on February 17, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

GHSA-cgwq-6prq-8h9q: microsoft/microsoft-graph Information Disc…

EPSS Exploitation Probability

via FIRST.org ↗

2.2%probability of exploitation in next 30 days

Lower Risk80th percentile+2.05%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

2 pkgs affected

🐘microsoft/microsoft-graph🐘microsoft/microsoft-graph

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

Impact

The Microsoft Graph PHP SDK published packages which contained test code that enabled the use of the phpInfo() function from any application that could access and execute the file at vendor/microsoft/microsoft-graph/tests/GetPhpInfo.php. The phpInfo function exposes system information.

The vulnerability affects the GetPhpInfo.php script of the PHP SDK which contains a call to the phpinfo() function.

This vulnerability requires a misconfiguration of the server to be present so it can be exploited. For example, making the PHP application’s /vendor directory web accessible.

The combination of the vulnerability and the server misconfiguration would allow an attacker to craft an HTTP request that executes the phpinfo() method. The attacker would then be able to get access to system information like configuration, modules, and environment variables and later on use the compromised secrets to access additional data.

Patches

This problem has been patched in versions 1.109.1 and 2.0.0-RC5.

Workarounds

If an immediate deployment with the updated vendor package is not available, you can perform the following temporary workarounds:

delete the vendor/microsoft/microsoft-graph/tests/GetPhpInfo.php file
remove access to the /vendor directory will remove this vulnerability
disable the phpinfo function

References

For more information about the vulnerability and the patch, users can refer to the following sources:

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`microsoft/microsoft-graph`	≥ 1.16.0&&< 1.109.1	1.109.1
🐘Packagist	`microsoft/microsoft-graph`	≥ 2.0.0-RC1&&< 2.0.1	2.0.1

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for microsoft/microsoft-graph. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update microsoft/microsoft-graph to 1.109.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-cgwq-6prq-8h9q is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-cgwq-6prq-8h9q is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-cgwq-6prq-8h9q. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact The Microsoft Graph PHP SDK published packages which contained test code that enabled the use of the phpInfo() function from any application that could access and execute the file at vendor/microsoft/microsoft-graph/tests/GetPhpInfo.php. The phpInfo function exposes system information. The vulnerability affects the GetPhpInfo.php script of the PHP SDK which contains a call to the phpinfo() function. This vulnerability requires a misconfiguration of the server to be present so it can be exploited. For example, making the PHP application’s /vendor directory web accessible. T

O3 Security · Impact-Aware SCA

Is GHSA-cgwq-6prq-8h9q in your dependencies?

O3 detects GHSA-cgwq-6prq-8h9q across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works

GHSA-cgwq-6prq-8h9q

EPSS Exploitation Probability

Blast Radius

Description

Impact

Patches

Workarounds

References

Affected Packages

Detection & mitigation playbook

Detect

Fix

Workarounds

How O3 protects you

Frequently Asked Questions

Is GHSA-cgwq-6prq-8h9q in your dependencies?