CVE-2025-10875
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 · uneditedImproper Neutralization of Input Used for LLM Prompting vulnerability in Salesforce Mulesoft Anypoint Code Builder allows Code Injection.This issue affects Mulesoft Anypoint Code Builder: before 1.11.6.
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 confidenceThis is an improper neutralization of input used for LLM prompting vulnerability in Mulesoft Anypoint Code Builder. User-supplied input is not properly sanitized before being used in prompts sent to an LLM, allowing attackers to inject malicious prompts and potentially execute arbitrary code or manipulate LLM behavior.
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.11.6CVSS 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
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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.
-
Confirm Anypoint Code Builder installationCheck if Mulesoft Anypoint Code Builder is installed in your environment. This may be visible in your IDE extensions (VS Code or Anypoint Platform), or listed in installed software. Look for 'Mulesoft Anypoint Code Builder' or 'Anypoint Code Builder' in your system.Affected if The product is installed and you are using version 1.11.5 or earlier, or if the version cannot be determined and is assumed to be below 1.11.6.
-
Identify the installed versionOpen Anypoint Code Builder (typically accessible via Anypoint Platform or IDE extension). Navigate to the product's 'About' or 'Version' information panel, or run any version query command if available in your setup. Alternatively, check the Anypoint Platform dashboard for the Code Builder version details.Affected if The displayed version is anything less than 1.11.6.
-
Determine if LLM integration is in useReview your Anypoint Code Builder configurations and project setups for any active connections to LLM services, AI assistants, or prompt-based features. Check for configured AI/LLM extensions, custom integrations, or any features that send user input to LLM prompts.Affected if LLM prompting or AI integration features are enabled and user-supplied input can be passed to LLM queries within Code Builder.
-
Inspect project configurations for prompt injection pointsExamine any custom scripts, extensions, or integrations within your Code Builder projects that handle user input and forward it to LLM prompts. Look for configuration files or extension settings that define how user input is processed before being sent to AI/LLM services.Affected if There are active integrations that pass unsanitized user input to LLM prompts without apparent input validation or sanitization.
You are affected if Mulesoft Anypoint Code Builder is installed with a version below 1.11.6 and you have LLM integration or AI prompting features enabled where user input could be injected into LLM prompts.
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.11.6
Upgrade Mulesoft Anypoint Code Builder to version 1.11.6 or later to remediate this vulnerability.
1.11.6
- Upgrade Mulesoft Anypoint Code Builder to version 1.11.6 or later to resolve the code injection vulnerability
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation6.0 h
- Testing3.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 $3,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-10875 — 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-10875 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