CVE-2025-64319
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 · uneditedIncorrect Permission Assignment for Critical Resource vulnerability in Salesforce Mulesoft Anypoint Code Builder allows Manipulating Writeable Configuration Files.This issue affects Mulesoft Anypoint Code Builder: before 1.12.1
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 confidenceAn incorrect permission assignment vulnerability in Mulesoft Anypoint Code Builder allows unauthorized users or processes to manipulate writable configuration files. This permission misconfiguration could enable an attacker to modify critical application settings, potentially leading to altered application behavior, privilege escalation, or injection of malicious configurations.
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< 1.12.1CVSS 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
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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.
-
Check installed Anypoint Code Builder versionRun 'anypoint-code-builder --version' from command line, or in VS Code check the Anypoint Code Builder extension version under Extensions > InstalledAffected if Version is below 1.12.1 (e.g., 1.12.0, 1.11.x, or earlier)
-
Locate Anypoint Code Builder configuration filesIdentify configuration files in the Anypoint Code Builder workspace, typically under the .anypoint or config directories where application settings, environment variables, and deployment configurations are storedAffected if Writable configuration files exist in the workspace
-
Inspect file system permissions on configuration filesUse OS commands to list file permissions: on Windows run 'icacls <config_file>' or on Unix/Linux run 'ls -la <config_file>' for each configuration file foundAffected if Write permissions (W) are granted to unauthorized users, groups, or 'Everyone'/'World'
-
Identify all users with write access to config directoriesRun 'icacls <config_directory>' on Windows or 'getfacl <config_directory>' on Linux to enumerate all principals granted write or modify permissionsAffected if Untrusted users, groups, or processes are listed as having write access
A user is affected if Anypoint Code Builder version is below 1.12.1 AND writable configuration files grant write access to unauthorized principals.
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.
dbcve · scoped1.12.1
Upgrade Mulesoft Anypoint Code Builder to version 1.12.1 or later. Review and enforce proper file system permissions on configuration files, ensuring only authorized users and processes have write access to critical configuration resources.
1.12.1
- Verify current Mulesoft Anypoint Code Builder version by accessing the Anypoint Platform and navigating to the Code Builder settings or about section
- Review the current project's compatibility with version 1.12.1 before upgrading
- Access Anypoint Platform administration console and navigate to the Anypoint Code Builder settings
- Initiate the upgrade to version 1.12.1 following the platform's update mechanism
- After upgrading, verify that the installation completed successfully by checking the version number
- Test critical workflows and configuration files to ensure proper functionality post-upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-64319 — 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-64319 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