dbcve.org
Command InjectionWeakness · CWE-77

CVE-2025-2733

MEDIUM · 6.3 CVSS v3.1 Published 2025-03-25
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 classified as critical has been found in mannaandpoem OpenManus up to 2025.3.13. This affects an unknown part of the file app/tool/python_execute.py of the component Prompt Handler. The manipulation leads to os command injection. It is possible to initiate the attack 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

OS command injection vulnerability in OpenManus app/tool/python_execute.py in the Prompt Handler component allows remote attackers to execute arbitrary OS commands via unspecified vectors in the prompt handling logic.

MitigationImplement strict input validation and sanitization on all user-controlled inputs before passing to OS commands. Replace unsafe shell execution methods with safer alternatives such as subprocess with shell=False and argument lists, or use sandboxed execution environments.

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. Locate the vulnerable python_execute.py file
    Search for the file 'app/tool/python_execute.py' in your OpenManus installation directory. Use: find / -path '*/app/tool/python_execute.py' 2>/dev/null or locate the file via your package manager if installed system-wide.
    Affected if The file exists in your environment, indicating OpenManus is installed with the vulnerable component.
  2. Verify the Prompt Handler component is in use
    Check if your OpenManus deployment exposes a prompt handling interface (web UI, API endpoint, or CLI that processes prompts). Review your configuration files and startup logs for prompt-related routes or handlers.
    Affected if The Prompt Handler component is actively configured or exposed, making it reachable for potential exploitation.
  3. Inspect python_execute.py for unsafe command execution
    Examine the contents of app/tool/python_execute.py and look for patterns such as: os.system(), subprocess.call(shell=True), subprocess.run(shell=True), or similar calls that pass user input to shell commands without sanitization.
    Affected if The file contains unsafe shell execution methods and accepts external input through the prompt handling logic.
  4. Check for user-controlled input flow to command execution
    Trace how prompts are processed: identify if prompt data flows from HTTP requests, CLI arguments, or configuration files into the command execution functions in python_execute.py without validation.
    Affected if User-supplied prompt input can reach the vulnerable command execution code path.
  5. Review network exposure of the prompt handling interface
    Determine if the Prompt Handler is accessible over the network (listen address 0.0.0.0, exposed port, or reverse proxy). Check your server configuration and firewall rules.
    Affected if The vulnerable component is network-accessible, increasing the risk of remote exploitation.

You are affected if OpenManus with the app/tool/python_execute.py file is installed and the Prompt Handler component is accessible, with the vulnerable code processing untrusted input through unsafe OS command execution.

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

Implement strict input validation and sanitization on all user-controlled inputs before passing to OS commands. Replace unsafe shell execution methods with safer alternatives such as subprocess with shell=False and argument lists, or use sandboxed execution environments.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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