CVE-2025-64321
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 Manipulating Writeable Configuration Files.This issue affects Agentforce Vibes Extension: before 3.3.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 prompt injection attacks that can manipulate writable configuration files. Attackers can craft malicious inputs that are processed by the LLM without proper sanitization, leading to unauthorized configuration modifications.
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.3.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
- 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.
-
Identify if Agentforce Vibes Extension is installedCheck the installed packages or extensions in your Salesforce org for Agentforce Vibes. This can be done through Salesforce Setup > Installed Packages or the extension management console.Affected if Agentforce Vibes Extension appears in the installed packages list
-
Determine the installed version of Agentforce VibesView the package details for Agentforce Vibes in your installed packages list and note the version number displayed.Affected if The version number is lower than 3.3.0 (for example, 3.2.0, 3.2.1, etc.)
-
Verify if the extension is active or enabledCheck the extension status or configuration settings in Salesforce to confirm whether Agentforce Vibes is currently active and processing inputs.Affected if The extension status shows as active, enabled, or running
-
Inspect configuration files for unexpected modificationsReview any writable configuration files associated with Agentforce Vibes (such as settings, preferences, or custom configuration objects) for unauthorized or unexpected changes that may indicate exploitation.Affected if Configuration files contain values or settings that were not intentionally created or modified by your administrators
Your environment is affected if Agentforce Vibes Extension is installed, enabled, and running at a version lower than 3.3.0.
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.3.0
Upgrade Agentforce Vibes Extension to version 3.3.0 or later to obtain the vendor patch that properly neutralizes prompt injection vectors.
3.3.0
- Identify the current installed version of Agentforce Vibes Extension in your Salesforce environment
- Navigate to the Salesforce AppExchange or your org's package management to obtain the latest version
- Upgrade Agentforce Vibes Extension to version 3.3.0 or later
- Verify the upgrade was successful by checking the installed version number
- Test the extension functionality to ensure proper operation after upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation2.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 $3,392.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-64321 — 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-64321 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