VulnerabilityPublished 10 Jun 2025Updated 11 Jun 2025

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

Affects Salesforce OmniStudioSource CVE Database V5

Not known to be exploited · CVSS 9.1 Critical.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score

9.1Critical

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

EPSS: 0.4% chance of exploitation in 30 days – higher than 41% 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:H/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
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: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to 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 26 Oct 2026.

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 or the CVSS exploit maturity 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

Immediate upgrade to the Spring 2025 release of Salesforce OmniStudio once available, as this version addresses the vulnerability.
Until patches are applied, restrict network access to Salesforce OmniStudio environments by implementing IP whitelisting and VPN requirements to limit exposure to trusted users and networks.
Review and tighten Salesforce user roles and permissions, minimizing privileges and enforcing the principle of least privilege to reduce the potential impact of exploitation.
Implement monitoring and alerting for unusual access patterns or data queries within Salesforce OmniStudio, focusing on attempts to access restricted fields.
Conduct regular audits of field-level security settings and validate that permissions are correctly enforced across all Salesforce objects.
Engage with Salesforce support and subscribe to security advisories to receive timely updates on patches and mitigation guidance.
Consider deploying Web Application Firewalls (WAF) with custom rules to detect and block suspicious API calls or queries targeting field-level data. These measures collectively reduce the attack surface and help detect or prevent exploitation while awaiting official patches.

Description

Improper Preservation of Permissions vulnerability in Salesforce OmniStudio (FlexCards) allows bypass of field level security controls for Salesforce objects. This impacts OmniStudio: before Spring 2025

Impact

For European organizations, the impact of this vulnerability is substantial due to the widespread adoption of Salesforce products, including OmniStudio, across various sectors such as finance, healthcare, retail, and public services. Unauthorized access to sensitive customer or internal data could lead to severe data breaches, violating GDPR and other data protection regulations, resulting in legal penalties and reputational damage. The ability to bypass field-level security controls undermines trust in Salesforce's data protection capabilities and could facilitate insider threats or external attackers gaining elevated access. This could lead to exposure of personally identifiable information (PII), financial data, or intellectual property. Additionally, compromised data integrity may affect business processes and decision-making. The absence of required authentication or user interaction for exploitation increases the risk of automated attacks targeting vulnerable Salesforce OmniStudio deployments. Given the criticality of the vulnerability, European organizations using affected versions must prioritize remediation to maintain compliance and protect sensitive data assets.

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, 02:18 UTC

WeaknessesCWE-281

Technical details

References

Community reviews

Related threats