dbcve.org
WebitrApplication · Uniong

CVE-2025-9255

HIGH · 7.5 CVSS v3.1 Published 2025-08-22
Fix available
A fix is available. Upgrade to 2_1_0_33 or later.
See remediation →
84/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
WebITR developed by Uniong has a SQL Injection vulnerability, allowing unauthenticated remote attackers to inject arbitrary SQL commands to read database contents.

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 · moderate confidence

WebITR by Uniong contains an unauthenticated SQL injection vulnerability allowing remote attackers to inject arbitrary SQL commands via unsanitized input parameters, enabling extraction of database contents.

MitigationImplement parameterized queries or prepared statements for all database operations, apply input validation, and deploy a WAF as a temporary compensating control until the vendor releases a patch.

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
WebitrApplication
Affected:< 2_1_0_33

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
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm WebITR is deployed
    Identify Uniong WebITR application in your environment by reviewing installed web applications, checking web server configurations, or scanning for 'WebITR' or 'Uniong' identifiers in HTTP responses or application metadata.
    Affected if WebITR by Uniong is present in the environment
  2. Identify installed version
    Locate the version number of the WebITR installation. Check application configuration files, the main application page footer, or the '/about' or '/version' endpoints if available. Compare against the affected version range: less than 2_1_0_33.
    Affected if The installed version is less than 2_1_0_33
  3. Verify unauthenticated parameter access
    Identify the input parameters used by WebITR that handle user-supplied data (e.g., query parameters, form fields, headers). Attempt to access these parameters without authentication to confirm they are reachable without credentials.
    Affected if Input parameters are accessible without authentication
  4. Check for SQL error disclosure
    Submit intentionally malformed SQL syntax (e.g., single quotes, OR 1=1) to identified input parameters and observe whether detailed database error messages are returned in the HTTP response.
    Affected if Database error messages are exposed in application responses, indicating unsanitized input handling

The environment is affected if Uniong WebITR is present with a version below 2_1_0_33 and unauthenticated input parameters are accessible without authentication.

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
Upgrade available Upgrade to 2_1_0_33 or later
Fixed in 2_1_0_33
Interim mitigation

Implement parameterized queries or prepared statements for all database operations, apply input validation, and deploy a WAF as a temporary compensating control until the vendor releases a patch.

Recommended fix Moderate confidence

Webitr version 2_1_0_33 or later

  1. 1. Verify the current installed version of Webitr by checking the application documentation or system files
  2. 2. Download the latest stable release of Webitr version 2_1_0_33 or later from the official vendor source
  3. 3. Before upgrading, backup the current database and configuration files to prevent data loss
  4. 4. Follow the vendor's official upgrade instructions for your deployment method (web interface, command line, or package manager)
  5. 5. After upgrading, verify the new version number matches the expected fixed version (2_1_0_33 or later)
  6. 6. Test that the application functions normally and confirm the SQL injection vulnerability is no longer exploitable
  7. 7. Review access logs to check for any prior exploitation attempts
Caveat Review vendor release notes for any configuration changes or deprecated features between your current version and 2_1_0_33

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

Fix this in Webitr Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
27.0 hours of engineering $4,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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