dbcve.org
Lookup ServerApplication · Nextcloud

CVE-2019-5476

CRITICAL · 9.8 CVSS v3.1 Published 2019-08-07
Fix available
A fix is available. Upgrade to 0.3.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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
An SQL Injection in the Nextcloud Lookup-Server < v0.3.0 (running on https://lookup.nextcloud.com) caused unauthenticated users to be able to execute arbitrary SQL commands.

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

A critical SQL Injection vulnerability in Nextcloud Lookup-Server versions prior to v0.3.0 allowed unauthenticated remote attackers to execute arbitrary SQL commands due to unsanitized input in database queries. The flaw was present in the lookup.nextcloud.com service.

MitigationUpgrade the Nextcloud Lookup-Server to version v0.3.0 or later to remediate the SQL injection vulnerability. If immediate patching is not feasible, consider disabling or restricting access to the Lookup-Server until the update can be applied.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Lookup ServerApplication
Affected:< 0.3.0

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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. Determine if you operate a self-hosted Lookup Server
    Review your infrastructure to identify if you have deployed your own Nextcloud Lookup-Server instance separate from the hosted lookup.nextcloud.com service. Check for any local installation or deployment of the lookup-server component.
    Affected if You run your own Lookup-Server instance in your environment.
  2. Locate the Lookup-Server installation directory
    If you operate a self-hosted Lookup-Server, identify its installation path. Common locations include /var/www/lookup-server, /opt/lookup-server, or within your container orchestration system if deployed as containers.
    Affected if You can locate the Lookup-Server installation directory.
  3. Find the installed version number
    Check the version file, git tags, or package metadata in the installation directory. Common files to inspect include VERSION, version.php, package.json, or use 'git describe --tags' if it's a git repository. Also check your package manager if installed via apt, yum, or similar.
    Affected if The version reported is below 0.3.0 or you cannot determine the version.
  4. Verify database connectivity configuration
    Examine the configuration file that defines database connection settings (typically config.php, config.yaml, or .env). Confirm that the Lookup-Server is configured to use a database backend, as the SQL injection flaw requires database queries to be executable.
    Affected if The Lookup-Server is connected to a database backend.
  5. Review access to the Lookup-Server
    Determine whether the Lookup-Server is exposed to network access, particularly the internet. Check firewall rules, reverse proxy configurations, and web server vhost settings for the Lookup-Server endpoint.
    Affected if The Lookup-Server is network-accessible from untrusted networks.

You are affected if you operate a self-hosted Nextcloud Lookup-Server instance and its installed version is below 0.3.0.

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
Upgrade available Upgrade to 0.3.0 or later
Fixed in 0.3.0
Interim mitigation

Upgrade the Nextcloud Lookup-Server to version v0.3.0 or later to remediate the SQL injection vulnerability. If immediate patching is not feasible, consider disabling or restricting access to the Lookup-Server until the update can be applied.

Recommended fix Moderate confidence

Upgrade to Lookup Server v0.3.0 or later

  1. Identify the current version of Nextcloud Lookup Server by checking the installation or git tags
  2. Stop the Lookup Server service to prevent any active connections during upgrade
  3. Backup the existing database and configuration files
  4. Update to version 0.3.0 or later by pulling the latest code from the Nextcloud Lookup Server repository
  5. Run any database migration scripts included in the new version
  6. Restart the Lookup Server service
  7. Verify the installation by checking that the version is now 0.3.0 or higher
  8. Test that the Lookup Server responds normally

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

Fix this in Lookup Server Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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