dbcve.org
InjectionWeakness · CWE-74

CVE-2025-1157

MEDIUM · 6.3 CVSS v3.1 Published 2025-02-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
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
A vulnerability was found in Allims lab.online up to 20250201 and classified as critical. This issue affects some unknown processing of the file /model/model_recuperar_senha.php. The manipulation of the argument recuperacao leads to sql injection. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used. 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 confidence

SQL injection vulnerability in Allims lab.online's password recovery function (/model/model_recuperar_senha.php). The 'recuperacao' parameter is not properly sanitized before use in SQL queries, allowing remote attackers to inject malicious SQL commands. Public exploit is available, increasing exploit likelihood.

MitigationReplace dynamic SQL queries with parameterized queries or prepared statements. Validate and sanitize all user inputs. Apply vendor patch if available, or implement input validation and least-privilege database accounts as compensating controls.

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

CVSS:3.1/AV:N/AC:L/PR:L/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. Confirm the Allims lab.online application is in use
    Inspect HTTP responses, check application branding, or review deployed web application files for 'lab.online' or 'Allims' identifiers
    Affected if The deployed web application is Allims lab.online
  2. Verify the vulnerable script file exists
    Check for the presence of /model/model_recuperar_senha.php in the web root directory
    Affected if The file model_recuperar_senha.php exists in the /model/ directory
  3. Confirm the password recovery function is accessible
    Access the password recovery URL endpoint (such as /recuperar_senha or the direct PHP script) via HTTP GET or POST
    Affected if The password recovery function is publicly or internally accessible
  4. Inspect the recuperacao parameter handling
    Review the source code of model_recuperar_senha.php to check if the 'recuperacao' POST/GET parameter is used in SQL queries without parameterized queries, prepared statements, or input sanitization
    Affected if The 'recuperacao' parameter is directly concatenated into SQL queries without escaping or parameterization
  5. Test for SQL injection susceptibility
    Submit a SQL injection payload (such as a single quote or boolean-based test) in the 'recuperacao' parameter and observe the application response for SQL errors or unexpected behavior
    Affected if The application returns SQL syntax errors or behaves differently based on injection payloads, indicating unsanitized input is used in queries

A user is affected if they run Allims lab.online with the model_recuperar_senha.php file accessible and the 'recuperacao' parameter processed without SQL parameterization.

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

Replace dynamic SQL queries with parameterized queries or prepared statements. Validate and sanitize all user inputs. Apply vendor patch if available, or implement input validation and least-privilege database accounts as compensating controls.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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