CVE-2023-49103
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.
- CVSS
- 10.0Criticalscored by the publisher (CNA)
- Exploited in the wild
- Yes, in CISA KEV since 30 Nov 2023CISA deadline for US federal agencies: 21 Dec 2023unvetted proof-of-concept code on github
- EPSS
- 77.8%chance of exploitation in the next 30 daystop 0.5% of scored CVEsFIRST score of 11 Nov 2026
- Fix
- Patch availablesee the advisories in the references
- Published
- 21 Nov 2023analysed here 12 Nov 2026
Do first. Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable. (CISA's required action for this KEV entry)
Summary
Triage
The summary, impact and action text on this page are written by our AI analysis pipeline, or taken from the NVD description when a CVE was imported from NVD. They are not the vendor's wording: check them against the sources. A longer AI executive summary and technical analysis are generated for signed-in accounts on the Max plan.
Affected products
Products named in our analysis
- owncloud:graph_api
Fix and mitigation
WAF and other mitigations
Can a WAF block it? Partly. The vulnerability is triggered by accessing a specific URL provided by the graphapi app that reveals sensitive PHP environment information. A web application firewall can block requests to this particular URL to prevent unauthorized information disclosure. A WAF rule can match access to the specific GetPhpInfo.php URL endpoint. No tracked WAF vendor has published a rule for this CVE yet, so you would write it yourself.
What a custom rule would match: access to the specific GetPhpInfo.php URL endpoint
Also consider: patch · custom WAF rule · response filtering
Based on an AI reading of the CVE description, and no vendor rule found yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.
Remediation steps (AI-written)
Step-by-step remediation is generated for accounts on the Max plan, for CVEs that match a technology in their stack. Add this technology to your stack to see the fix checklist.
Exploitation evidence
- CISA KEV catalog
- Listed since 30 Nov 2023.
- CISA due date
- 21 Dec 2023, the remediation deadline for US federal agencies
- CISA required action
- Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
- Public exploit code
- Unvetted proof-of-concept code on GitHub: 1 Metasploit module · 3 GitHub proofs of concept · 1 Nuclei template
- CISA SSVC
- exploitation active, automatable yes, technical impact partialAssessed by CISA 27 Jan 2025 (SSVC 2.0.3). Exploitation is none, poc (public proof of concept) or active.
Metasploit
- auxiliary/gather/owncloud_phpinfo_readerauxiliary, rank normal
Nuclei
- OwnCloud - Phpinfo Configurationdetection template, high
GitHub proofs of concept
- creacitysec/CVE-2023-4910330 stars
- merlin-ke/OwnCloud-CVE-2023-491031 stars
- d0rb/CVE-2023-491030 stars
Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.
Timeline
- 21 Nov 2023Published
- 22 Nov 2023First proof-of-concept repository on GitHub (unvetted)same day later
- 30 Nov 2023Added to CISA KEV (exploited in the wild)8 days later
- 21 Dec 2023CISA remediation due date (US federal agencies)21 days later
- 27 Jan 2025CISA SSVC assessment: exploitation active404 days (about 1 year) later
- 21 Oct 2025CVE record last updated267 days (about 9 months) later
- 12 Nov 2026Analysed by vulneraibility.com387 days (about 1 year) later
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
| Metric | Value | What it means |
|---|---|---|
| Attack vector | NetworkReachable over the internet or any routable network. | Reachable over the internet or any routable network. |
| Attack complexity | LowRepeatable attack, no special conditions. | Repeatable attack, no special conditions. |
| Privileges required | NoneThe attacker needs no prior access. | The attacker needs no prior access. |
| User interaction | NoneNo victim action needed. | No victim action needed. |
| Scope | ChangedImpact crosses a security boundary into other components. | Impact crosses a security boundary into other components. |
| Confidentiality | HighTotal data disclosure possible. | Total data disclosure possible. |
| Integrity | HighComplete modification possible. | Complete modification possible. |
| Availability | HighFull outage possible. | Full outage possible. |
Common questions
Is CVE-2023-49103 being exploited?
Yes. CVE-2023-49103 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.
How severe is CVE-2023-49103?
CVE-2023-49103 is rated Critical with a CVSS score of 10.0. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2023-49103?
Yes. A fix has been recorded for CVE-2023-49103. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2023-49103 affect?
CVE-2023-49103 affects owncloud:graph_api. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
References
3 references in the CVE record, grouped by the tags the record gives them.
Other links (3)
- owncloud.org /security
- owncloud.com /security-advisories/disclosure-of-sensitive-credentials-and-configuration-in-co
- cisa.gov /known-exploited-vulnerabilities-catalog?field_cve=CVE-2023-49103
Where the data on this page comes from
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- CISA KEV catalog: exploitation, date added, due date
- CISA Vulnrichment (ADP): SSVC decision points
- FIRST EPSS: exploit probability and percentile
- Metasploit Framework: exploit and scanner modules
- Nuclei templates: detection templates
- PoC-in-GitHub: GitHub repositories that claim a proof of concept
Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.
Similar CVEs
Get CVEs like this by email. Join the free digest: the CVEs we flag as major, all CVSS 8.0 or higher, in up to three emails a day (sent at 05:00, 11:00 and 15:00 UTC). Matching alerts to the products you run needs an account, and accounts are invite-only during the beta.