dbcve.org
UryApplication

CVE-2025-13168

CRITICAL · 9.8 CVSS v3.1 Published 2025-11-14
Fix available
A fix is available. Upgrade to 0.2.1 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click Patch available

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 weakness has been identified in ury-erp ury up to 0.2.0. This affects the function overrided_past_order_list of the file ury/ury/api/pos_extend.py. This manipulation of the argument search_term causes sql injection. Remote exploitation of the attack is possible. The exploit has been made available to the public and could be exploited. Upgrading to version 0.2.1 is able to mitigate this issue. Patch name: 063384e0dddfd191847cd2d6524c342cc380b058. It is suggested to upgrade the affected component. The vendor replied and reacted very professional.

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 overrided_past_order_list function within ury/ury/api/pos_extend.py. The search_term parameter is not properly sanitized before use in SQL queries, allowing remote attackers to inject malicious SQL commands via the unsanitized input.

MitigationUpgrade ury-erp to version 0.2.1 which contains the patch (commit 063384e0dddfd191847cd2d6524c342cc380b058) that properly sanitizes the search_term parameter to prevent SQL injection.

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
UryApplication
Affected:< 0.2.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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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. Check installed Ury version
    Run 'pip show ury-erp' or check your package management system for the installed version of the ury-erp package. Compare against the vulnerable range: versions prior to 0.2.1
    Affected if The installed version is below 0.2.1
  2. Locate the vulnerable file
    Find the file at path 'ury/ury/api/pos_extend.py' in your installation directory. Use 'find' command or check your package installation location
    Affected if The file exists in your environment
  3. Identify the vulnerable function
    Open pos_extend.py and locate the 'overrided_past_order_list' function definition. Verify it accepts a 'search_term' parameter
    Affected if The function exists and accepts search_term as input
  4. Inspect SQL query handling of search_term
    Within the overrided_past_order_list function, examine how the search_term parameter is used in SQL queries. Look for direct string concatenation or unsanitized interpolation into SQL statements without parameterized queries
    Affected if search_term is used directly in SQL queries without sanitization (e.g., no parameterized queries, no escaping)
  5. Determine if the vulnerable endpoint is exposed
    Check if there is a route or API endpoint that maps to the overrided_past_order_list function and is accessible to remote users (check your API routing configuration or urls.py)
    Affected if The function is exposed via an accessible API endpoint

You are affected if your installed ury-erp version is below 0.2.1, the vulnerable file exists, and the overrided_past_order_list function uses the search_term parameter unsanitized in SQL queries while being accessible via an API endpoint.

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 0.2.1 or later
Fixed in 0.2.1
Vendor patch github.com →
Interim mitigation

Upgrade ury-erp to version 0.2.1 which contains the patch (commit 063384e0dddfd191847cd2d6524c342cc380b058) that properly sanitizes the search_term parameter to prevent SQL injection.

Recommended fix High confidence

0.2.1

  1. 1. Back up your current ury-erp installation and database before upgrading.
  2. 2. Upgrade the ury-erp component from version 0.2.0 or earlier to version 0.2.1 or later.
  3. 3. Verify the upgrade was successful by checking the installed version.
  4. 4. Test the application functionality, particularly the `overrided_past_order_list` function in the POS extended API, to confirm the SQL injection vulnerability is resolved.

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

Fix this in Ury Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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