NextcloudpiApplication · Nextcloud

CVE-2024-30247

CRITICAL · 9.8 CVSS v3.1 Published 2024-03-29
Fix available
A fix is available. Upgrade to 1.53.1 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
NextcloudPi is a ready to use image for Virtual Machines, Raspberry Pi, Odroid HC1, Rock64 and other boards. A command injection vulnerability in NextCloudPi allows command execution as the root user via the NextCloudPi web-panel. Due to a security misconfiguration this can be used by anyone with access to NextCloudPi web-panel, no authentication is required. It is recommended that the NextCloudPi is upgraded to 1.53.1.

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 command injection vulnerability in NextCloudPi's web-panel allows unauthenticated attackers to execute arbitrary commands as the root user due to a security misconfiguration. The flaw is exploitable by anyone with network access to the NextCloudPi web interface, requiring no authentication.

MitigationUpgrade NextCloudPi to version 1.53.1 or later to remediate the command injection vulnerability. If immediate patching is not possible, restrict network access to the web-panel until the upgrade can be performed.

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
NextcloudpiApplication
Affected:< 1.53.1

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. Confirm NextCloudPi installation
    Check if NextCloudPi is installed by looking for the web-panel service. On the system, run: dpkg -l | grep -i nextcloudpi or systemctl status ncp 2>/dev/null | head -10
    Affected if The system is running NextCloudPi software
  2. Identify installed NextCloudPi version
    Run: sudo ncp-report or check /usr/local/bin/ncp and /var/www/ncp-version for version information. Alternatively, access the web-panel and check the dashboard for the version number.
    Affected if The installed version is less than 1.53.1 (e.g., 1.53.0, 1.52.x, etc.)
  3. Verify web-panel network accessibility
    Check if the NextCloudPi web interface (typically port 443 or 4443) is listening on an external or reachable network interface. Run: netstat -tlnp | grep -E '443|4443' or ss -tlnp | grep -E '443|4443'
    Affected if The web-panel is bound to 0.0.0.0 or an externally accessible IP address, making it network-exploitable

The environment is affected if NextCloudPi is installed with a version prior to 1.53.1 AND the web-panel is network-accessible, allowing unauthenticated root command execution.

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 1.53.1 or later
Fixed in 1.53.1
Interim mitigation

Upgrade NextCloudPi to version 1.53.1 or later to remediate the command injection vulnerability. If immediate patching is not possible, restrict network access to the web-panel until the upgrade can be performed.

Recommended fix High confidence

1.53.1

  1. Backup all NextCloudPi data before performing the upgrade
  2. Access the NextCloudPi web-panel or use the command-line interface to initiate the upgrade
  3. Run the upgrade process to update NextCloudPi to version 1.53.1
  4. After upgrade completes, verify the system is functioning correctly and the version is 1.53.1

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

Fix this in Nextcloudpi 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 the upgrade done

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-2024-30247 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

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-2024-30247 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