dbcve.org
Incorrect Default PermissionsWeakness · CWE-276

CVE-2025-52361

HIGH · 7.8 CVSS v3.1 Published 2025-08-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
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
Insecure permissions in the script /etc/init.d/lighttpd in AK-Nord USB-Server-LXL Firmware v0.0.16 Build 2023-03-13 allows a locally authenticated low-privilege user to execute arbitrary commands with root privilege via editing this script which is executed with root-privileges on any interaction and on every system boot.

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

The /etc/init.d/lighttpd script in AK-Nord USB-Server-LXL Firmware v0.0.16 has insecure file permissions allowing any locally authenticated low-privilege user to modify it. Since this init script executes with root privileges on boot and service interactions, an attacker can inject arbitrary commands to achieve root-level code execution.

MitigationChange ownership to root and restrict permissions on /etc/init.d/lighttpd to read/execute only for non-root users (e.g., chown root:root /etc/init.d/lighttpd && chmod 755 /etc/init.d/lighttpd). Audit all other init scripts in /etc/init.d/ for similar permission vulnerabilities.

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

CVSS:3.1/AV:L/AC:L/PR:L/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. Check firmware version
    Identify the installed firmware version of AK-Nord USB-Server-LXL using vendor-specific commands or by examining system information files (e.g., /etc/version, /proc/version, or the web management interface).
    Affected if The firmware version is v0.0.16 or falls within the affected range.
  2. Verify lighttpd init script exists
    Check if the file /etc/init.d/lighttpd exists on the system using: ls -la /etc/init.d/lighttpd
    Affected if The file /etc/init.d/lighttpd exists on the system.
  3. Inspect file ownership and permissions
    Run: ls -la /etc/init.d/lighttpd to view the owner, group, and permission bits.
    Affected if The file is not owned by root, OR the permission bits allow write access for group (g+w) or others (o+w), meaning non-root users can modify the script.
  4. Confirm writable access for non-root users
    If permissions show write access for group or others (such as 775, 777, 665, 667, or any mode with w in the g or o field), test write access with a non-privileged account or verify the permission bits mathematically.
    Affected if Any authenticated user without root privileges can write to /etc/init.d/lighttpd.

You are affected if you are running AK-Nord USB-Server-LXL Firmware v0.0.16 and the /etc/init.d/lighttpd script exists with permissions that allow non-root users to write to it (any write bit set for group or others).

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

Change ownership to root and restrict permissions on /etc/init.d/lighttpd to read/execute only for non-root users (e.g., chown root:root /etc/init.d/lighttpd && chmod 755 /etc/init.d/lighttpd). Audit all other init scripts in /etc/init.d/ for similar permission vulnerabilities.

Recommended fix Moderate confidence

AK-Nord USB-Server-LXL Firmware version newer than v0.0.16 Build 2023-03-13 (contact vendor for specific patched release)

  1. 1. Connect to the AK-Nord USB-Server-LXL device via SSH or console with administrative/root credentials
  2. 2. Verify the current permissions on /etc/init.d/lighttpd using: ls -la /etc/init.d/lighttpd
  3. 3. Check file ownership using: stat /etc/init.d/lighttpd
  4. 4. If the file is world-writable or writable by a low-privilege user, change the permissions to 755 (rwxr-xr-x) using: chmod 755 /etc/init.d/lighttpd
  5. 5. Ensure the file is owned by root:root using: chown root:root /etc/init.d/lighttpd
  6. 6. Verify the fix by confirming only root can write to the file: ls -la /etc/init.d/lighttpd
  7. 7. Reboot the device to ensure the init script still functions correctly
Caveat Modifying init script permissions may require verification that automatic updates do not revert the permissions; ensure backup of configuration exists before making changes

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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