CVE-2025-43701VulnerabilityPublished 10 Jun 2025

CVE-2025-43701: Salesforce OmniStudio · Improper Preservation of Permissions

Affects Salesforce OmniStudioSource CVE Database V5

Not known to be exploited · CVSS 7.5 High.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.4% chance of exploitation in 30 days – higher than 38% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 10 Jun 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Salesforce OmniStudio	Affected =0	Fixed in–

AI-suggested

European organizations should prioritize upgrading Salesforce OmniStudio to version 254 or later as soon as the patch becomes available. Until then, they should implement strict network-level access controls to limit exposure of OmniStudio interfaces to trusted IP ranges and internal networks only. Monitoring and logging access to OmniStudio FlexCards and Custom Settings data should be enhanced to detect any anomalous or unauthorized access attempts. Organizations should conduct thorough audits of Custom Settings data to identify and minimize sensitive information stored there, applying the principle of least privilege. Additionally, implementing Web Application Firewalls (WAFs) with custom rules to detect and block suspicious requests targeting OmniStudio endpoints can provide a temporary protective layer. Security teams should also review and tighten Salesforce user permissions and roles to reduce the attack surface. Finally, organizations should prepare incident response plans specific to Salesforce environments to quickly address any potential exploitation.

Description

Improper Preservation of Permissions vulnerability in Salesforce OmniStudio (FlexCards) allows exposure of Custom Settings data. This impacts OmniStudio: before version 254.

Impact

For European organizations using Salesforce OmniStudio, this vulnerability poses a significant risk to the confidentiality of sensitive business data. Exposure of Custom Settings could reveal internal configurations, API keys, or business logic parameters that attackers might use to escalate privileges, conduct targeted attacks, or exfiltrate further data. Given the widespread adoption of Salesforce products across various sectors in Europe, including finance, healthcare, and public services, the breach of such data could lead to regulatory non-compliance under GDPR, reputational damage, and financial losses. The fact that exploitation requires no authentication or user interaction increases the risk of automated scanning and exploitation attempts. Organizations relying on OmniStudio for customer engagement or internal workflows may face operational risks if attackers leverage the exposed data to craft sophisticated attacks or social engineering campaigns. Additionally, the exposure of sensitive configuration data could undermine trust in digital services and complicate incident response efforts.

CWE-281Improper Preservation of Permissions (opens in a new tab)
Base weaknessOWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product does not preserve permissions or incorrectly preserves permissions when copying, restoring, or sharing objects, which can cause them to have less restrictive permissions than intended.
OWASP Cheat Sheets
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.8 (opens in a new tab)
V13.4.2 (opens in a new tab)
V7.2.2 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

help.salesforce.com/s/articleView?id=004980323&type=1 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 11 Jul 2025, 00:33 UTC

WeaknessesCWE-281

Technical details

References

Community reviews

Related threats