dbcve.org
QuipuxApplication

CVE-2025-55343

CRITICAL · 9.9 CVSS v3.1 Published 2025-11-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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
Quipux 4.0.1 through e1774ac allows authenticated users to conduct SQL injection attacks via busqueda/busqueda.php txt_depe_codi, busqueda/busqueda.php txt_usua_codi, anexos_lista.php radi_temp, Administracion/listas/formArea_ajax.php codDepe, Administracion/listas/formDepeHijo_ajax.php codDepe, Administracion/listas/formDepePadre_ajax.php codInst, asociar_documentos/asociar_borrar_referencia.php radi_nume, asociar_documentos/asociar_documento_buscar_query.php radi_nume, asociar_documentos/asociar_documento_grabar.php txt_radi_nume, asociar_documentos/asociar_documento radi_nume, radicacion/buscar_usuario.php buscar_tipo, radicacion/formArea_ajax.php codDepe, radicacion/formDepeHijo_ajax.php codDepe, radicacion/formDepePadre_ajax.php codInst, radicacion/ver_datos_usuario.php destinatorio, reportes/reporte_TraspasoDocFisico.php verrad, tx/datos_imprimir_sobre.php txt_usua_codi, tx/datos_imprimir_sobre.php nume_radi_temp, tx/revertir_firma_digital_grabar.php txt_radi_nume, tx/tx_borrar_opcion_imp.php codigo_opc, tx/tx_realizar_tx.php txt_radicados, tx/tx_seguridad_documentos.php txt_radicados, or uploadFiles/cargar_doc_digitalizado_paginador.php txt_depe_codi.

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

Multiple SQL injection vulnerabilities in Quipux 4.0.1 through e1774ac allow authenticated users to execute arbitrary SQL commands via unsanitized parameters in 20+ PHP files including busqueda/busqueda.php, anexos_lista.php, various Administracion/listas, asociar_documentos, radicacion, reportes, tx, and uploadFiles modules. Parameters such as txt_depe_codi, txt_usua_codi, codDepe, radi_nume, and txt_radicados are directly used in SQL queries without proper input validation or parameterized queries.

MitigationImplement parameterized queries/prepared statements for all database interactions across affected files, apply strict input validation and sanitization, and apply principle of least privilege to database accounts. Upgrade to patched version if available.

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
QuipuxApplication
Affected:= 4.0.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
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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 Quipux version
    Locate the version file or check the application header/admin interface for the installed Quipux version number
    Affected if The installed version is exactly 4.0.1 (note: other versions may also be affected but this CVE specifies 4.0.1)
  2. Locate vulnerable PHP files
    Search the web application directory for the following files mentioned in the advisory: busqueda/busqueda.php, anexos_lista.php, and any PHP files within Administracion, asociar_documentos, radicacion, reportes, tx, and uploadFiles directories
    Affected if Any of these PHP files exist in the application webroot
  3. Verify authentication is required
    Confirm that the Quipux application requires user authentication to access the affected modules
    Affected if The application allows unauthenticated access to the vulnerable endpoints (the CVE states authenticated users can exploit, so unauthenticated access would also be concerning)
  4. Review SQL query implementation
    Examine source code of the affected PHP files and search for direct usage of parameters txt_depe_codi, txt_usua_codi, codDepe, radi_nume, and txt_radicados in SQL queries without parameterized queries or input sanitization
    Affected if These parameters are used directly in SQL queries without prepared statements or validation
  5. Check database user privileges
    Review the database configuration to determine if the application database user has only necessary privileges (excessive privileges would compound the impact)
    Affected if The database user has administrative or elevated privileges beyond what the application requires

You are affected if you are running Quipux version 4.0.1 and have the vulnerable PHP files present with the authentication requirement as described in the CVE.

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 parameterized queries/prepared statements for all database interactions across affected files, apply strict input validation and sanitization, and apply principle of least privilege to database accounts. Upgrade to patched version if available.

Fix this in Quipux Scoped from the published advisory
  • Consultation12.0 h
  • Implementation60.0 h
  • Testing24.0 h
  • Review / QA16.0 h
112.0 hours of engineering $19,680
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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