# CVE-2023-49283: Test code in published microsoft-graph-core package exposes phpinfo() > An attacker can access system configuration details via exposed test code if the vendor directory is web-accessible, requiring server misconfiguration. - **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:L`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 5 Dec 2023 - **Updated:** 10 Oct 2024 - **Also known as:** GHSA-mhhp-c3cm-2r86 ## What is CVE-2023-49283? CVE-2023-49283 is a medium-severity vulnerability in microsoftgraph msgraph-sdk-php-core, published on 5 Dec 2023. Any signed-in user can exploit it over the network, with no action from the victim. ### Official description microsoft-graph-core the Microsoft Graph Library for PHP. The Microsoft Graph Beta 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. This problem has been patched in version 2.0.2. 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, or disable the phpinfo function Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor) ## Which versions are affected by CVE-2023-49283? 2 open source packages ship an affected version, including microsoft/microsoft-graph-core. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `microsoft/microsoft-graph-core` | Packagist | All versions | 2.0.2 | | `microsoft/microsoft-graph-core` | Packagist | All versions | 2.0.2 | Products: Microsoft Graph. ## How do I fix CVE-2023-49283? Upgrade microsoft/microsoft-graph-core to 2.0.2 or later. ## Is CVE-2023-49283 being exploited? There is no known exploitation of CVE-2023-49283 in the wild and no public exploit code. ## Other vulnerabilities in microsoftgraph msgraph-sdk-php-core - [CVE-2026-49159](https://insights.sbomify.com/CVE-2026-49159/): Microsoft Graph Information Disclosure Vulnerability (medium 6.5) - [CVE-2026-47655](https://insights.sbomify.com/CVE-2026-47655/): Microsoft Graph Information Disclosure Vulnerability (medium 6.5) - [CVE-2023-49282](https://insights.sbomify.com/CVE-2023-49282/): Test code in published microsoft-graph package exposes phpinfo() (medium 5.4) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2023-49283 and fix it if it is affected. What it is: CVE-2023-49283 is a medium-severity vulnerability in microsoftgraph msgraph-sdk-php-core, published on 5 Dec 2023. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2023-49283 in the wild and no public exploit code. Affected packages and fixed versions: - microsoft/microsoft-graph-core (Packagist): affected all versions; fixed in 2.0.2 - microsoft/microsoft-graph-core (Packagist): affected all versions; fixed in 2.0.2 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-2023-49283/ (Markdown: https://insights.sbomify.com/CVE-2023-49283/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2023-49283 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-49283 - OSV: https://osv.dev/vulnerability/CVE-2023-49283 --- From sbomify Insights: https://insights.sbomify.com/CVE-2023-49283/ Summaries are generated and may contain mistakes; the official description above is the record.