CVE-2025-2954
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 · uneditedA vulnerability, which was classified as problematic, was found in mannaandpoem OpenManus up to 2025.3.13. This affects the function execute of the file app/tool/file_saver.py of the component File Handler. The manipulation leads to improper access controls. Local access is required to approach this attack. 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 confidenceA local improper access control vulnerability exists in OpenManus up to 2025.3.13 within the file_saver.py component's execute function. An attacker with local access can manipulate file operations to bypass access controls, potentially allowing unauthorized file read/write operations. The vulnerability has been publicly disclosed.
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<= 2025.3.13CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/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 checksWork through these to decide whether this CVE applies to you.
-
Locate OpenManus installationSearch for the OpenManus directory on the system. Common locations include user home directories, /opt/, or project directories. Look for a folder named 'OpenManus' or 'openmanus'.Affected if OpenManus is found on the system and its version is 2025.3.13 or earlier
-
Identify the installed versionCheck for version information in the installation directory. Look for version files (VERSION, __version__.py), git tags, or check the source code for version constants. The vulnerability affects versions up to and including 2025.3.13.Affected if Version is 2025.3.13 or any earlier version <= 2025.3.13
-
Verify file_saver.py existsLocate the file_saver.py file within the OpenManus source code. It should be in the agent or tool handling code paths. Search for files containing 'file_saver' in the name.Affected if The file_saver.py component exists in the installation
-
Inspect execute function in file_saver.pyOpen file_saver.py and locate the 'execute' function. Examine the function for access control implementation: look for path traversal checks, file permission validations, or authorization logic before file operations.Affected if The execute function exists but lacks proper access control validation (no path traversal prevention, no permission checks, or no authorization enforcement before file read/write operations)
-
Check for community patchesSearch the local installation for any patch files, modified versions of file_saver.py, or security hardening that may have been applied by the user or community.Affected if No patches or hardening modifications have been applied to file_saver.py
A user is affected if OpenManus version 2025.3.13 or earlier is installed and the file_saver.py execute function lacks access control validation.
Generated from the published advisory. Verify against your own configuration.
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 dataImplement proper access control validation in the execute function of file_saver.py, including path traversal prevention, file permission checks, and restricting file operations to authorized paths only. Since the vendor did not respond, users should apply community patches or manually harden the file handler.
- Consultation3.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-2954 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-2954 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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