CVE-2023-49282

CVE-2023-49282 is a medium-severity security vulnerability in microsoft/microsoft-graph (composer), affecting versions >= 1.16.0, < 1.109.1. It is fixed in 1.109.1, 2.0.1.

Does this CVE actually affect you?

Kodem shows which CVEs are reachable and running in your applications, so you fix what's exploitable, not just what's listed.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Runtime intelligence, not another scanner.

Summary

Test code in published microsoft-graph package exposes phpinfo()

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:

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.

CVE-2023-49282 has a CVSS score of 5.4 (Medium). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.109.1, 2.0.1); upgrading removes the vulnerable code path.

Affected versions

microsoft/microsoft-graph (>= 1.16.0, < 1.109.1) microsoft/microsoft-graph (>= 2.0.0-RC1, < 2.0.1)

Security releases

microsoft/microsoft-graph → 1.109.1 (composer) microsoft/microsoft-graph → 2.0.1 (composer)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environmentNew to Kodem? Get a demo →

Remediation advice

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

Frequently Asked Questions

  1. What is CVE-2023-49282? CVE-2023-49282 is a medium-severity security vulnerability in microsoft/microsoft-graph (composer), affecting versions >= 1.16.0, < 1.109.1. It is fixed in 1.109.1, 2.0.1.
  2. How severe is CVE-2023-49282? CVE-2023-49282 has a CVSS score of 5.4 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
  3. Which versions of microsoft/microsoft-graph are affected by CVE-2023-49282? microsoft/microsoft-graph (composer) versions >= 1.16.0, < 1.109.1 is affected.
  4. Is there a fix for CVE-2023-49282? Yes. CVE-2023-49282 is fixed in 1.109.1, 2.0.1. Upgrade to this version or later.
  5. Is CVE-2023-49282 exploitable, and should I be worried? Whether CVE-2023-49282 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
  6. What actually determines whether CVE-2023-49282 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
  7. How do I fix CVE-2023-49282?
    • Upgrade microsoft/microsoft-graph to 1.109.1 or later
    • Upgrade microsoft/microsoft-graph to 2.0.1 or later

Stop the waste.
Protect your environment with Kodem.