dbcve.org
Server-Side Request Forgery (SSRF)Weakness · CWE-918

CVE-2025-53828

HIGH · 8.5 CVSS v3.1 Published 2026-07-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
91/100
Remediation priority · Urgent
Remotely reachable Zero-click 7 weeks old

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
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.

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

This is a Server-Side Request Forgery (SSRF) vulnerability in the SharePoint for ownCloud application that allows an attacker with administrative privileges to execute arbitrary code on the system. The vulnerability exists in SharePoint for ownCloud versions prior to 0.4.1, corresponding to ownCloud 10 versions prior to 10.15.3.

MitigationUpgrade ownCloud 10 to version 10.15.3 or later to receive SharePoint for ownCloud version 0.4.1, which contains the fix for this SSRF vulnerability enabling arbitrary code execution.

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

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
High
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

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

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. Verify SharePoint for ownCloud is installed
    Check the ownCloud apps directory or use the ownCloud occ command: occ app:list | grep -i sharepoint. Also inspect ownCloud's app configuration database table for sharepoint app entry.
    Affected if The SharePoint for ownCloud app appears in the installed apps list
  2. Check SharePoint for ownCloud version
    Run: occ app:list --verbose | grep -A5 sharepoint or inspect the appinfo/info.xml file within the sharepoint app directory to find the version number.
    Affected if The installed version is lower than 0.4.1 or the version field is missing/unparseable
  3. Check ownCloud 10 core version
    Run: occ --version or inspect the ownCloud config.php file (version element) in the ownCloud data directory.
    Affected if The ownCloud 10 version is lower than 10.15.3
  4. Confirm SharePoint app is enabled
    Run: occ app:list | grep -i sharepoint to verify the app status shows as enabled, or check the oc_appconfig table in the ownCloud database for the sharepoint app entry with enabled=1.
    Affected if The SharePoint app is enabled and active in the ownCloud instance

Your environment is affected if SharePoint for ownCloud is installed and enabled with a version prior to 0.4.1 on ownCloud 10 versions prior to 10.15.3.

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 ownCloud 10 to version 10.15.3 or later to receive SharePoint for ownCloud version 0.4.1, which contains the fix for this SSRF vulnerability enabling arbitrary code execution.

Recommended fix High confidence

ownCloud 10.15.3 (which includes SharePoint for ownCloud 0.4.1)

  1. 1. Back up your current ownCloud 10 installation and database before upgrading.
  2. 2. Review the ownCloud 10.15.3 release notes for any specific migration requirements.
  3. 3. Upgrade ownCloud 10 to version 10.15.3 or later following the official ownCloud upgrade documentation.
  4. 4. Verify that the SharePoint for ownCloud app is updated to version 0.4.1 or later.
  5. 5. Confirm the upgrade was successful by logging in and checking the app versions.
  6. 6. Test that the SharePoint integration functionality works correctly after the upgrade.
Caveat Review ownCloud 10.15.3 release notes for any breaking changes; always test upgrades in a staging environment before production deployment

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-53828 — 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-2025-53828 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