Test code in published microsoft-graph-core package exposes phpinfo()GHSA-mhhp-c3cm-2r86
MEDIUMGHSA-mhhp-c3cm-2r86 is a medium-severity (CVSS 5.4) Information Exposure vulnerability in microsoft/microsoft-graph-core. A fix is available for microsoft/microsoft-graph-core — see the affected versions and patch details below.
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-mhhp-c3cm-2r86.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
microsoft/microsoft-graph-coreReal-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 Core 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-core/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 version 2.0.2.
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-core/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:
- https://nvd.nist.gov/vuln/detail/CVE-2023-49103
- https://github.com/microsoftgraph/msgraph-beta-sdk-php/compare/2.0.0...2.0.1
- https://github.com/microsoftgraph/msgraph-sdk-php-core/compare/2.0.1...2.0.2
- https://github.com/microsoftgraph/msgraph-sdk-php/compare/1.109.0...1.109.1
- https://owncloud.com/security-advisories/disclosure-of-sensitive-credentials-and-configuration-in-containerized-deployments/
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | microsoft/microsoft-graph-core | all versions | 2.0.2composer require microsoft/microsoft-graph-core:^2.0.2 |
Affected Products
graphmicrosoftDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for microsoft/microsoft-graph-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update microsoft/microsoft-graph-core to 2.0.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mhhp-c3cm-2r86 is resolved across your whole dependency graph.
Workarounds
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.
Frequently Asked Questions
Is GHSA-mhhp-c3cm-2r86 in your dependencies?
Find it across Packagist, including transitive dependencies.