CVE-2023-49105: An issue was discovered in ownCloud owncloud/core before 10.13.1.
An issue was discovered in ownCloud owncloud/core before 10.13.1. An attacker can access, modify, or delete any file without authentication if the username of a victim is known, and the victim has no signing-key configured. This occurs because pre-signed URLs can be accepted even when no signing-key is configured for the owner of the files. The earliest affected version is 10.6.0.
Security readout for executives and security teams
Plain-English summary
A flaw in ownCloud Core can let an unauthenticated attacker read, alter, or delete a user’s files when the username is known and that user lacks a signing key. Because compromise requires no credentials or user interaction and can affect file confidentiality, integrity, and availability, exposed vulnerable installations warrant immediate attention.
Executive priority
Treat this as an immediate remediation and investigation priority. The vulnerability can compromise or destroy stored files without credentials, and CISA confirms known exploitation. Identify vulnerable ownCloud installations, upgrade them, assess potentially exposed accounts, and review evidence of unauthorized file activity.
Technical view
CVE-2023-49105 is an authentication bypass affecting ownCloud Core versions from 10.6.0 through versions before 10.13.1. The WebDAV API can accept pre-signed URLs when the file owner has no signing key configured. The CVSS 3.1 score is 9.8, reflecting network reachability, low complexity, no privileges, no interaction, and high impact.
Likely exposure
Exposure exists where ownCloud Core 10.6.0 through 10.13.0 is deployed and users lack signing keys. An attacker must know a victim’s username. Internet-accessible services present the clearest risk, but reachable internal deployments may also be exposed.
Exploitation context
CISA lists CVE-2023-49105 in its Known Exploited Vulnerabilities catalog, supporting active exploitation in the wild. The supplied sources do not establish exploitation prevalence, affected victim counts, or whether public exploit tooling is available.
Researcher notes
The vulnerable condition combines acceptance of pre-signed URLs without an owner signing key, knowledge of a username, and an affected Core version. CWE-287 applies. The supplied evidence does not describe request details, indicators of compromise, exploit reliability, or complete forensic artifacts, so validation should remain non-invasive and vendor-guided.
Mitigation direction
Upgrade affected ownCloud Core installations to version 10.13.1 or later.
Follow the ownCloud advisory for vendor-approved remediation and configuration guidance.
Restrict unnecessary network access to ownCloud until remediation is verified.
Prioritize backups and confirm recovery readiness for stored files.
Validation and detection
Inventory ownCloud Core versions and identify installations running 10.6.0 through 10.13.0.
Determine whether file owners have signing keys configured.
Confirm the deployed version is 10.13.1 or later after remediation.
Review access and audit logs for unexplained unauthenticated file reads, modifications, or deletions.
Verify important files and backups for unexpected changes or loss.
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-287: Credential and account abuse lookup
Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. 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.
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.
Exploitation: activeAutomatable: yesTechnical 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-287 · source CWE mapping
Improper Authentication
Improper Authentication represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.