dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 21 Dec 2023.
Graph ApiApplication · Owncloud

CVE-2023-49103

HIGH · 7.5 CVSS v3.1 Published 2023-11-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
In the wild High EPSS Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
An issue was discovered in ownCloud owncloud/graphapi 0.2.x before 0.2.1 and 0.3.x before 0.3.1. The graphapi app relies on a third-party GetPhpInfo.php library that provides a URL. When this URL is accessed, it reveals the configuration details of the PHP environment (phpinfo). This information includes all the environment variables of the webserver. In containerized deployments, these environment variables may include sensitive data such as the ownCloud admin password, mail server credentials, and license key. Simply disabling the graphapi app does not eliminate the vulnerability. Additionally, phpinfo exposes various other potentially sensitive configuration details that could be exploited by an attacker to gather information about the system. Therefore, even if ownCloud is not running in a containerized environment, this vulnerability should still be a cause for concern. Note that Docker containers from before February 2023 are not vulnerable to the credential disclosure.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The ownCloud graphapi app (versions 0.2.x before 0.2.1 and 0.3.x before 0.3.1) includes a third-party GetPhpInfo.php library that exposes a URL revealing full phpinfo() output. This exposes all PHP environment variables including sensitive data such as admin passwords, mail credentials, and license keys in containerized deployments. Simply disabling the graphapi app does not remediate the issue.

MitigationUpgrade graphapi app to version 0.2.1 or 0.3.1 to remove the vulnerable GetPhpInfo.php library. Note that disabling the app alone does not eliminate the vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Graph ApiApplication
Affected:= 0.2.0= 0.3.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify graphapi app version
    Check the version of the installed ownCloud graphapi app. This is typically found in the ownCloud marketplace, app settings, or by inspecting the appinfo/info.xml file in the graphapi app directory.
    Affected if The installed version is 0.2.0 or 0.3.0, or the version cannot be determined but falls within these release lines.
  2. Locate GetPhpInfo.php file
    Search for the GetPhpInfo.php file within the ownCloud graphapi application directory structure. Typical path pattern: /path/to/owncloud/apps/graphapi/vendor/microsoft/windowsazure/lib/GetPhpInfo.php or similar vendor directories.
    Affected if The GetPhpInfo.php file exists in the graphapi app directory or its vendor subdirectories.
  3. Check vulnerable URL accessibility
    Attempt to access the known vulnerable endpoint. The typical path is /index.php/apps/graphapi/vendor/microsoft/windowsazure/lib/GetPhpInfo.php or a variation that exposes the phpinfo output via the graphapi app routes.
    Affected if Accessing this URL returns the full phpinfo() output showing PHP configuration and environment variables.
  4. Verify sensitive data in environment
    If phpinfo output is accessible, inspect it for exposure of sensitive environment variables such as OC_PASS, mail server credentials, license keys, database credentials, or other secrets that should not be visible.
    Affected if The phpinfo output reveals environment variables containing passwords, keys, or other credentials.

You are affected if the graphapi app version is 0.2.0 or 0.3.0, OR the GetPhpInfo.php file exists and is accessible via web request, as either condition allows exposure of PHP environment variables containing sensitive credentials.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade graphapi app to version 0.2.1 or 0.3.1 to remove the vulnerable GetPhpInfo.php library. Note that disabling the app alone does not eliminate the vulnerability.

Recommended fix High confidence

graphapi version 0.2.1 or 0.3.1 (or latest stable)

  1. Upgrade the ownCloud graphapi app to version 0.2.1 or 0.3.1 (or the latest stable version available)
  2. After upgrading, verify the vulnerability is fixed by attempting to access the GetPhpInfo.php endpoint and confirming it no longer returns phpinfo output

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Graph Api Exploited in the wild — priority engagement
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-49103 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-49103 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data