CVE-2025-5178
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 · uneditedA vulnerability classified as critical has been found in Realce Tecnologia Queue Ticket Kiosk up to 20250517. Affected is an unknown function of the file /adm/ajax.php of the component Image File Handler. The manipulation of the argument files[] leads to unrestricted upload. It is possible to launch the attack remotely. The vendor was contacted early about this disclosure but did not respond in any way.
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 confidenceUnrestricted file upload vulnerability in /adm/ajax.php within the Image File Handler component of Realce Tecnologia Queue Ticket Kiosk. The files[] argument is not properly validated, allowing attackers to upload arbitrary file types including executable code. This critical (CVSS 9.8) vulnerability is remotely exploitable without authentication.
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<= 2025-05-17CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify if Realcetecnologia Queue Ticket Kiosk is installedCheck your web server for the presence of the Queue Ticket Kiosk application. Common locations include /var/www/html/, /home/, or C:\inetpub\. Look for application directories containing the typical queue kiosk interface files.Affected if The application is present on the system.
-
Locate the vulnerable ajax.php endpointCheck if the file /adm/ajax.php exists within the application directory. This is the specific endpoint for the Image File Handler component mentioned in the CVE.Affected if The file /adm/ajax.php exists and is accessible via HTTP/HTTPS.
-
Verify the endpoint allows unauthenticated accessAttempt to access the /adm/ajax.php endpoint without providing any authentication credentials (cookies, tokens, or session data). Observe whether the server responds with the upload functionality rather than rejecting the request with an authentication error.Affected if The endpoint responds to unauthenticated requests without requiring login.
-
Test for unrestricted file uploadSend a POST request to /adm/ajax.php with the files[] parameter containing a test file (e.g., a harmless text file or a PHP file). Observe whether the server accepts and stores the file without validating its extension, content-type, or magic bytes.Affected if The endpoint accepts and stores files without performing extension validation, content-type checking, or magic byte verification.
-
Confirm uploads are web-accessibleIf files are accepted, check if they are stored in a web-accessible directory (within the web root). Attempt to access the uploaded file via a direct URL to determine if it can be executed by the web server.Affected if Uploaded files are stored in a web-accessible location and can be directly accessed via URL.
If the Queue Ticket Kiosk application is present with an accessible /adm/ajax.php endpoint that accepts unauthenticated file uploads without proper validation and stores them in a web-accessible location, the environment is affected by CVE-2025-5178.
Generated from the published advisory. Verify against your own configuration.
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 dataImplement strict allowlist-based file validation (checking both extension AND magic bytes/content-type), store uploads outside the webroot or with non-executable permissions, and add proper authentication/authorization checks to the upload endpoint.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-5178 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-5178 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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