CVE-2025-53828: SharePoint for ownCloud 10 is vulnerable to Server-Side Request Forgery (SSRF)
SharePoint for ownCloud is an application for using SharePoint with the file storage, synchronization, and sharing application ownCloud Classic. In SharePoint for ownCloud prior to version 0.4.1, which corresponds to ownCloud 10 prior to 10.15.3, an attacker with administrative privileges can use a SSRF vulnerability in the SharePoint app to execute arbitrary code on the system. Upgrade ownCloud 10 to version 10.15.3 or later to receive SharePoint for ownCloud 0.4.1, the fixed version.
Security readout for executives and security teams
Plain-English summary
A flaw in the SharePoint app for ownCloud 10 lets someone who already has administrator access reach into internal systems the server can see and use that access to run code on the ownCloud host. The risk is limited to environments where an attacker has already obtained admin credentials, but the outcome is full compromise of the ownCloud server.
Executive priority
Treat as a high-priority patch for teams running ownCloud 10 with the SharePoint integration, but not a fire-drill for externally exposed exploitation. Schedule the upgrade to 10.15.3 in the next standard patch window and confirm administrator credential hygiene; there is no evidence of active exploitation at this time.
Technical view
CVE-2025-53828 is a Server-Side Request Forgery (CWE-918) in the SharePoint for ownCloud application affecting versions before 0.4.1, bundled with ownCloud 10 before 10.15.3. An authenticated administrator can abuse the SharePoint integration to issue attacker-controlled server-side requests, which the advisory says can be chained into arbitrary code execution. CVSS 3.1 is 8.5 (AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H) reflecting scope change and high impact.
Likely exposure
Any ownCloud 10 deployment older than 10.15.3 that has the SharePoint app enabled is exposed. Because exploitation requires administrative privileges, direct external mass exploitation is unlikely, but stolen or shared admin credentials, insider misuse, or a chained privilege escalation would put the host at risk of full compromise.
Exploitation context
No public exploit, proof-of-concept, or in-the-wild activity is cited in the provided sources, and the CVE is not listed in CISA KEV. The vendor advisory (GHSA-4m66-rpfj-m5f6) describes the impact as SSRF leading to arbitrary code execution when triggered by an administrator. Attack complexity is rated High, and authentication as an administrator is required.
Researcher notes
CWE-918 with Scope:Changed and RCE outcome suggests the SSRF primitive can reach a sensitive internal endpoint that returns or triggers code execution paths, though the advisory does not disclose the specific sink. PR:L combined with the vendor's "administrative privileges" wording indicates the attacker must already be an ownCloud admin. Worth watching for follow-on write-ups since AC:H and privilege gating limit weaponization, but a chained auth-bypass would sharply raise urgency.
Mitigation direction
Upgrade ownCloud 10 to 10.15.3 or later, which delivers SharePoint for ownCloud 0.4.1.
If patching is delayed, disable the SharePoint for ownCloud app until the upgrade is applied.
Restrict and audit ownCloud administrator accounts, enforcing MFA and least privilege.
Egress-filter the ownCloud server so it cannot reach internal metadata or management endpoints.
Monitor ownCloud admin activity and outbound requests originating from the app server.
Validation and detection
Confirm ownCloud core version is 10.15.3 or newer and SharePoint app is at 0.4.1 or newer.
Inventory instances where the SharePoint for ownCloud app is installed or enabled.
Review administrator account list, recent logins, and any unexpected privilege grants.
Check web and proxy logs for unusual outbound requests from the ownCloud host to internal ranges.
Verify vendor advisory GHSA-4m66-rpfj-m5f6 against your deployment's current build.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-918: Information exposure and cloud metadata lookup
Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
The CVE wording references SSRF or metadata access, so cloud discovery and credential material review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
2Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-918 · source CWE mapping
Server-Side Request Forgery (SSRF)
Server-Side Request Forgery (SSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.