AimApplication · Aimstack

CVE-2025-5321

CRITICAL · 9.9 CVSS v3.1 Published 2025-05-29
Fix available
A fix is available. Upgrade to after 3.29.1 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit 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 classified as critical was found in aimhubio aim up to 3.29.1. This vulnerability affects the function RestrictedPythonQuery of the file /aim/storage/query.py of the component run_view Object Handler. The manipulation of the argument Abfrage leads to erweiterte Rechte. The attack can 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 · moderate confidence

A critical privilege escalation vulnerability exists in aimhubio aim (versions up to 3.29.1) within the RestrictedPythonQuery function in /aim/storage/query.py. The run_view Object Handler improperly handles the 'Abfrage' argument, allowing remote attackers to manipulate this input to gain elevated/extended privileges beyond their assigned permissions.

MitigationImplement strict input validation on the 'Abfrage' argument and enforce proper authorization checks within the RestrictedPythonQuery function to ensure users can only access data permitted by their actual privilege level.

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
AimApplication
Affected:<= 3.29.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
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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. Identify Aim installation and version
    Run 'pip show aim' or check your package manager to get the installed version of aimhubio aim. Compare the version number to the affected range (<= 3.29.1).
    Affected if The installed version is 3.29.1 or lower.
  2. Locate the vulnerable query.py file
    Find the file /aim/storage/query.py in your Aim installation directory. This file contains the RestrictedPythonQuery function that contains the vulnerability.
    Affected if The file exists in your installation and the RestrictedPythonQuery function is present.
  3. Verify web/API exposure of RestrictedPythonQuery
    Check your Aim web interface or API endpoints that utilize the RestrictedPythonQuery function. Look for any endpoints that accept an 'Abfrage' parameter in requests.
    Affected if Endpoints handling the 'Abfrage' argument are accessible without proper authorization controls.
  4. Check user permission enforcement
    Review the authorization logic in the run_view Object Handler. Test whether low-privilege users can manipulate the 'Abfrage' argument to access data or functions outside their assigned permissions.
    Affected if Users can elevate privileges or access data beyond their assigned permission level through the 'Abfrage' parameter.

You are affected if Aim version 3.29.1 or lower is installed and the RestrictedPythonQuery function with 'Abfrage' argument handling is exposed without proper authorization checks.

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
Upgrade available Upgrade to a release after 3.29.1
Interim mitigation

Implement strict input validation on the 'Abfrage' argument and enforce proper authorization checks within the RestrictedPythonQuery function to ensure users can only access data permitted by their actual privilege level.

Fix this in Aim Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
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,968.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-5321 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

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-5321 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