CVE-2025-5176
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 was found in Realce Tecnologia Queue Ticket Kiosk up to 20250517. It has been declared as critical. This vulnerability affects unknown code of the file /adm/index.php of the component Admin Login Page. The manipulation of the argument Usuário leads to sql injection. The attack can be initiated 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 confidenceSQL injection vulnerability in Realce Tecnologia Queue Ticket Kiosk admin login page (/adm/index.php). The 'Usuário' (username) parameter is not properly sanitized before use in database queries, allowing remote attackers to inject malicious SQL commands. The 9.1 CVSS score reflects the critical nature of this auth bypass vector.
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
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
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 Realce Tecnologia Queue Ticket Kiosk is installedLocate the application by searching for files named 'index.php' in '/adm/' directory, or check web server document roots for folders containing 'Queue Ticket Kiosk' or 'Realcetecnologia' naming. Look for the presence of the /adm/index.php file.Affected if The application file /adm/index.php exists on the server and is identified as part of Realce Tecnologia Queue Ticket Kiosk.
-
Determine the installed versionCheck version information in application metadata (composer.json, package.json, README files, or version constants in PHP files within the application root). Compare the discovered version or build date to the affected range: versions with release date <= 2025-05-17.Affected if The installed version has a release date on or before 2025-05-17, or no version information is found (which may indicate an unpatched older release).
-
Verify the admin login endpoint is exposedAttempt to access or scan for the path /adm/index.php via HTTP/HTTPS request from an authorized internal position, or check web server access logs for requests to this endpoint.Affected if The /adm/index.php endpoint is accessible and returns a login form, indicating the vulnerable interface is exposed.
-
Confirm the vulnerable 'Usuário' parameter existsExamine the HTML source of the /adm/index.php login page and identify if a form field named 'Usuário' or its URL-encoded equivalent is present. Alternatively, inspect the PHP source code in /adm/index.php to locate the $_POST['Usuário'] or $_REQUEST['Usuário'] variable usage.Affected if The login form contains an input field named 'Usuário' (username) that is passed to backend database queries without visible sanitization.
-
Check for SQL injection mitigation in login codeReview the PHP source code of /adm/index.php around the login authentication logic. Search for use of prepared statements (PDO::prepare, mysqli_prepare) or lack thereof when handling the 'Usuário' parameter in SQL queries.Affected if The code constructs SQL queries using the 'Usuário' parameter directly (e.g., "SELECT...WHERE usuario='$usuario'") without parameterized queries, indicating the vulnerability is present.
A user is affected if they have Realce Tecnologia Queue Ticket Kiosk installed with a version dated on or before 2025-05-17, the /adm/index.php login page is accessible, and the 'Usuário' parameter is handled in SQL queries without prepared statements.
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.
dbcve · scopedImplement parameterized queries (prepared statements) for all database operations in the login functionality. Additionally, apply input validation and output encoding for the 'Usuário' parameter and ensure proper error handling that does not expose database details.
- 1. Implement a Web Application Firewall (WAF) rule to detect and block SQL injection attempts on the /adm/index.php endpoint
- 2. Apply input validation and sanitization on the 'Usuário' parameter before any database query execution
- 3. Use parameterized queries (prepared statements) instead of string concatenation for database operations
- 4. Contact Realce Tecnologia directly requesting a formal patch for CVE-2025-5176
- 5. If vendor remains unresponsive, consider isolating the admin login page via network segmentation or IP allow-listing
- 6. Monitor logs for SQL injection patterns targeting the login functionality
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing5.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 $4,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-5176 — 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-5176 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