CVE-2025-64320
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 Agentforce Vibes Extension allows Code Injection.This issue affects Agentforce Vibes Extension: before 3.2.0.
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 confidenceImproper neutralization of input in Salesforce Agentforce Vibes Extension allows code injection via LLM prompting. The extension fails to properly sanitize user-supplied input before incorporating it into LLM prompts, enabling attackers to inject malicious prompt content that could result in unauthorized code execution.
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< 3.2.0CVSS 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.
-
Identify Agentforce Vibes Extension versionLocate the installed version of the Salesforce Agentforce Vibes Extension in your Salesforce setup. This is typically found in the extension settings, package manager, or installed apps section of your Salesforce org.Affected if The installed version is lower than 3.2.0
-
Verify extension is enabledConfirm that the Agentforce Vibes Extension is actively enabled in your Salesforce environment. Check the extension status in your Salesforce setup or administration console.Affected if The extension is enabled and running
-
Check for LLM prompt functionalityIdentify if the Agentforce Vibes Extension is configured to use LLM prompting capabilities. Review the extension feature settings and configuration options related to prompt generation or AI interactions.Affected if LLM prompting features are configured and in use
-
Review user input handling in promptsExamine how user-supplied input flows through the Agentforce Vibes Extension to LLM prompts. Check for any custom configurations or integrations that pass user data to the extension without sanitization.Affected if User input can be incorporated into LLM prompts directly without input validation
If Agentforce Vibes Extension version is below 3.2.0 and LLM prompting is enabled with user input flowing to prompts, the environment is affected by this vulnerability.
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 · scoped3.2.0
Upgrade Agentforce Vibes Extension to version 3.2.0 or later to remediate the vulnerability.
3.2.0
- Identify the current version of Agentforce Vibes Extension installed in your Salesforce org
- Review current Agentforce Vibes Extension configurations and prompt templates for any customizations
- Back up current Agentforce Vibes Extension configuration data
- Navigate to the Salesforce AppExchange or Salesforce setup to obtain Agentforce Vibes Extension version 3.2.0 or later
- Upgrade the Agentforce Vibes Extension to version 3.2.0 or latest available version
- Verify the upgrade was successful by checking the installed package version
- Test Agentforce Vibes Extension functionality to ensure the code injection vulnerability is remediated
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-64320 — 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-64320 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