dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2025-0645

HIGH · 7.2 CVSS v3.1 Published 2025-11-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable 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
Unrestricted Upload of File with Dangerous Type vulnerability in Narkom Communication and Software Technologies Trade Ltd. Co. Pyxis Signage allows Accessing Functionality Not Properly Constrained by ACLs. This issue affects Pyxis Signage: through 31012025.

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 · moderate confidence

This is an unrestricted file upload vulnerability combined with an ACL (Access Control List) bypass in Pyxis Signage. Attackers can upload dangerous file types (e.g., executable scripts) without proper constraints, and can also access functionality that should be restricted by ACLs. The vulnerability affects versions through 31012025.

MitigationImplement strict file type validation using magic byte verification, restrict upload locations outside the web root, disable script execution in upload directories, and enforce proper ACL checks on all sensitive functionality endpoints.

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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/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. Identify if Pyxis Signage is installed
    Search for Pyxis Signage installation directories, services, or web applications on the system. Common locations include /opt/pyxis, /var/www/pyxis, or check for the pyxis service via 'systemctl list-units --type=service | grep -i pyxis'
    Affected if Pyxis Signage software is found running on the system
  2. Determine the installed version
    Check the version of Pyxis Signage by examining version files, the web interface footer, or running 'pyxis --version' or 'apt list --installed | grep -i pyxis' if using package management
    Affected if The installed version is 31012025 or any earlier version (versions through 31012025 are affected)
  3. Verify if file upload functionality is accessible
    Locate the file upload feature in the Pyxis Signage web interface (typically under media, content, or settings sections). Attempt to access the upload endpoint or check if unauthenticated or low-privilege users can reach upload functionality
    Affected if File upload interface is accessible without proper authentication or from untrusted network paths
  4. Inspect file upload restrictions
    Examine the application's upload configuration, form handlers, or API endpoints for file upload. Check if there are restrictions on file types, extensions, or content validation in the application config or code
    Affected if No file type validation is enforced, or dangerous extensions like .php, .js, .exe, .sh are explicitly allowed
  5. Check ACL enforcement on sensitive endpoints
    Test access to administrative or restricted functionality (user management, system settings, content control) using a standard or limited-privilege account. Verify that ACL checks are properly applied to sensitive API endpoints
    Affected if Restricted functionality is accessible without proper ACL validation or privilege checks pass incorrectly

If Pyxis Signage version 31012025 or earlier is running with accessible file upload functionality lacking proper validation, or if restricted endpoints can be accessed without correct ACL enforcement, the environment is vulnerable to CVE-2025-0645.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict file type validation using magic byte verification, restrict upload locations outside the web root, disable script execution in upload directories, and enforce proper ACL checks on all sensitive functionality endpoints.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
25.0 hours of engineering $4,400
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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