dbcve.org
InjectionWeakness · CWE-74

CVE-2025-1811

HIGH · 7.3 CVSS v3.1 Published 2025-03-02
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 vulnerability was found in AT Software Solutions ATSVD up to 3.4.1. It has been declared as critical. Affected by this vulnerability is an unknown functionality of the file /login.aspx of the component Login Endpoint. The manipulation of the argument txtUsuario leads to sql injection. The attack can be launched remotely. The exploit has been disclosed to the public and may be used. Upgrading to version 3.4.2 is able to address this issue. It is recommended to upgrade the affected component.

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 the login endpoint (/login.aspx) of AT Software Solutions ATSVD allows remote attackers to inject malicious SQL queries via the txtUsuario parameter. The vulnerability is exploitable without authentication and has a public exploit.

MitigationUpgrade ATSVD to version 3.4.2 or later to remediate this SQL 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. Confirm ATSVD application is present
    Locate the application by checking for the presence of login.aspx file in the web root directory, typically found at /login.aspx or within the ATSVD installation folder. Use file system search or web server configuration to identify the application path.
    Affected if The login.aspx file exists in the web directory, indicating ATSVD is installed and accessible.
  2. Identify ATSVD version
    Check the application version by inspecting assembly files (Web.config, version.dll, or release notes) within the ATSVD installation directory, or by accessing the application directly and looking for version information in the login page source or About section.
    Affected if The installed version is lower than 3.4.2, making it potentially vulnerable.
  3. Verify login endpoint accessibility
    Attempt to access the /login.aspx endpoint directly via HTTP/HTTPS request without authentication. Confirm the endpoint responds and displays a login form.
    Affected if The login page is accessible without authentication, which is required for exploitation.
  4. Confirm txtUsuario parameter exists
    Submit a GET or POST request to /login.aspx and inspect the form parameters. Verify that txtUsuario (or similar username field) is present in the login form submission.
    Affected if The txtUsuario parameter is present in the login form and accepts user-supplied input without sanitization.

If ATSVD with login.aspx is present, the version is below 3.4.2, and the login endpoint with txtUsuario parameter is accessible without authentication, the environment is affected by CVE-2025-1811.

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 ATSVD to version 3.4.2 or later to remediate this SQL injection vulnerability.

Recommended fix High confidence

AT Software Solutions ATSVD version 3.4.2

  1. 1. Backup the current ATSVD installation and database before proceeding with the upgrade.
  2. 2. Download the updated ATSVD version 3.4.2 from the vendor's official distribution channel.
  3. 3. Deploy version 3.4.2 to the affected server, replacing the previous installation.
  4. 4. Verify the login endpoint at /login.aspx is functioning correctly after the upgrade.
  5. 5. Test that the txtUsuario parameter no longer accepts SQL injection payloads.
  6. 6. Monitor the application logs for any unusual SQL activity to confirm the vulnerability is remediated.

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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