dbcve.org
InjectionWeakness · CWE-74

CVE-2025-13792

HIGH · 7.3 CVSS v3.1 Published 2025-11-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
Remotely reachable No privileges 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
A security flaw has been discovered in Qualitor up to 8.20.104/8.24.97. Affected by this vulnerability is the function eval of the file /html/st/stdeslocamento/request/getResumo.php. Performing a manipulation of the argument passageiros results in code injection. Remote exploitation of the attack is possible. The exploit has been released to the public and may be used for attacks. Upgrading to version 8.20.105 and 8.24.98 addresses this issue. Upgrading the affected component is advised.

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

Qualitor versions up to 8.20.104/8.24.97 contain a code injection vulnerability in /html/st/stdeslocamento/request/getResumo.php where the 'passageiros' parameter is passed to the unsafe eval() function, allowing remote attackers to execute arbitrary PHP code on the server.

MitigationUpgrade Qualitor to version 8.20.105 or 8.24.98 to remediate this code injection vulnerability.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

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. Verify Qualitor installation exists
    Locate Qualitor web application files in the web server document root (typically under /var/www/html, /www, or similar paths). Look for directories containing 'qualitor' or the specific vulnerable path /html/st/stdeslocamento/
    Affected if Qualitor is not found on the system - the check is not applicable
  2. Identify Qualitor version
    Check the installed version by inspecting version files in the Qualitor installation directory, or access the application's 'Sobre' (About) page if available. Compare the version number against 8.20.104 and 8.24.97.
    Affected if The installed version is 8.20.104 or lower, OR 8.24.97 or lower
  3. Confirm vulnerable script exists
    Verify the file /html/st/stdeslocamento/request/getResumo.php exists within the Qualitor web directory structure.
    Affected if The vulnerable PHP file is present in the installation
  4. Check for external exposure
    Determine if the Qualitor web application is accessible from untrusted networks (internet-facing or untrusted internal segments).
    Affected if The application is externally accessible and the version is within the affected range

The environment is affected if Qualitor is installed with version 8.20.104 or lower, or version 8.24.97 or lower, and the vulnerable getResumo.php script is present and reachable.

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

Upgrade Qualitor to version 8.20.105 or 8.24.98 to remediate this code injection vulnerability.

Recommended fix High confidence

8.20.105 or 8.24.98 (depending on installed branch)

  1. Identify the current Qualitor version installed (8.20.x or 8.24.x branch)
  2. Perform a full backup of the Qualitor database and application files
  3. Stop the Qualitor application services
  4. Upgrade Qualitor to version 8.20.105 if on the 8.20.x branch, or to version 8.24.98 if on the 8.24.x branch
  5. Restart the Qualitor application services
  6. Verify the upgrade was successful by checking the new version number
  7. Test the application functionality, specifically the affected endpoint /html/st/stdeslocamento/request/getResumo.php to confirm the vulnerability is fixed

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

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
26.0 hours of engineering $4,560
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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