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

CVE-2025-53830

CRITICAL · 9.1 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 →
97/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
Anti-Virus for ownCloud is an anti-virus application for file storage, synchronization, and sharing application ownCloud. Versions of Anti-Virus for ownCloud before 1.2.3 are vulnerable to Server-Side Request Forgery (SSRF). This corresponds to versions of ownCloud 10 prior to 10.15.3. Upgrade ownCloud 10 to version 10.15.3 or later or upgrade Anti-Virus for ownCloud 10 to version 1.2.3 or later to receive a fix.

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

Anti-Virus for ownCloud versions before 1.2.3 contain a Server-Side Request Forgery (SSRF) vulnerability, allowing attackers to make the server perform requests to arbitrary internal or external resources. This affects ownCloud 10 versions prior to 10.15.3.

MitigationUpgrade Anti-Virus for ownCloud to version 1.2.3 or later, or upgrade ownCloud 10 to version 10.15.3 or later, to patch the SSRF vulnerability.

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

CVSS:3.1/AV:N/AC:L/PR:H/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 Anti-Virus app is installed
    In ownCloud admin panel, navigate to Apps section and search for Anti-Virus, or list installed apps via occ command: 'occ app:list' and look for 'antivirus' in the output
    Affected if Anti-Virus app appears in the list of installed apps
  2. Check Anti-Virus app version
    Run 'occ app:version antivirus' or inspect the app's appinfo/info.xml file in ownCloud's apps directory to find the version number
    Affected if The reported version is lower than 1.2.3 (e.g., 1.2.2, 1.2.1, 1.2.0, etc.)
  3. Confirm Anti-Virus feature is enabled
    Navigate to ownCloud admin settings under 'Security' or 'Antivirus' section, or run 'occ config:app:get antivirus enabled' to check if the app is active
    Affected if The app is enabled and configured to scan uploaded files
  4. Check for custom antivirus server configuration
    In ownCloud admin antivirus settings, look for fields like 'Antivirus server URL' or 'ICAP endpoint' that accept custom URLs/hostnames. Run 'occ config:list antivirus' to dump current antivirus settings
    Affected if A custom URL endpoint is configured that could be manipulated via SSRF

You are affected if the Anti-Virus for ownCloud app is installed, enabled, running at a version before 1.2.3, and has the antivirus scanning feature active with a configurable URL endpoint.

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 Anti-Virus for ownCloud to version 1.2.3 or later, or upgrade ownCloud 10 to version 10.15.3 or later, to patch the SSRF vulnerability.

Recommended fix High confidence

ownCloud 10.15.3 or later / Anti-Virus for ownCloud 1.2.3 or later

  1. 1. Determine your current versions of ownCloud 10 and Anti-Virus for ownCloud by checking the ownCloud admin panel or command line
  2. 2. Create a complete backup of your ownCloud instance including database and file storage
  3. 3. Review ownCloud 10.15.3 release notes for any migration requirements or breaking changes
  4. 4. If running Anti-Virus for ownCloud, upgrade the Anti-Virus app to version 1.2.3 or later via the ownCloud marketplace or package manager
  5. 5. Alternatively, upgrade ownCloud 10 to version 10.15.3 or later by following the official upgrade documentation
  6. 6. After upgrade, verify the Anti-Virus for ownCloud application is functioning correctly
  7. 7. Test that file scanning operations work as expected
  8. 8. Verify the SSRF vulnerability is resolved by confirming the anti-virus scanner only processes expected URLs
Caveat Review ownCloud 10.15.3 release notes for any migration requirements; ensure PHP version compatibility and deprecated feature handling

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

Have this fixed Scoped from the published advisory
  • 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-2025-53830 — 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-53830 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