CVE-2023-49282 — microsoft/microsoft-graph
MEDIUMCVE-2023-49282 is a medium-severity (CVSS 5.4) Information Exposure vulnerability in microsoft/microsoft-graph. A fix is available for microsoft/microsoft-graph — see the affected versions and patch details below.
Test code in published microsoft-graph package exposes phpinfo()
EPSS Exploitation Probability
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.
How urgent is this, really
CVE-2023-49282 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 378,156 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
microsoft/microsoft-graph🐘microsoft/microsoft-graphReal-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:
- 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 | ≥ 1.16.0&&< 1.109.1 | 1.109.1composer require microsoft/microsoft-graph:^1.109.1 |
| 🐘Packagist | microsoft/microsoft-graph | ≥ 2.0.0-RC1&&< 2.0.1 | 2.0.1composer require microsoft/microsoft-graph:^2.0.1 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for microsoft/microsoft-graph, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
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 CVE-2023-49282 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2023-49282 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2023-49282. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2023-49282 in your dependencies?
O3 Security finds CVE-2023-49282 across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.