VulnerabilityPublished 4 Jan 2025Updated 6 Jan 2025

CVE-2025-22386: Optimizely Configured Commerce · Insufficient Session Expiration

Source CVE Database V5

Not known to be exploited · CVSS 7.3 High · fixed in 5.2.2408 : patch Optimizely Configured Commerce soon.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score

7.3High

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

EPSS: 0.2% chance of exploitation in 30 days – higher than 21% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Affects: Optimizely Configured Commerce before 5.2.2408
Patch: Available – fixed in 5.2.2408

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: Required
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: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
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 4 Jan 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

AI-suggested

Organizations should immediately review their use of Optimizely Configured Commerce and plan to upgrade to version 5.2.2408 or later once available. In the absence of an official patch, implement compensating controls such as enforcing shorter session timeouts, invalidating sessions server-side upon logout, and monitoring for unusual session reuse patterns. Employ multi-factor authentication (MFA) to reduce the impact of stolen session tokens. Additionally, ensure secure transmission of session tokens using HTTPS with secure and HttpOnly cookie flags. Conduct regular security audits and penetration testing focused on session management. Educate users about phishing risks and encourage prompt reporting of suspicious activity. Network segmentation and strict access controls can limit the scope of potential exploitation. Finally, stay informed on vendor advisories for official patches or updates.

Description

An issue was discovered in Optimizely Configured Commerce before 5.2.2408. A medium-severity session issue exists in the Commerce B2B application, affecting the longevity of active sessions in the storefront. This allows session tokens tied to logged-out sessions to still be active and usable.

Impact

The primary impact of CVE-2025-22386 is unauthorized access to user accounts within the Optimizely Configured Commerce B2B storefront environment. Attackers can exploit lingering session tokens to impersonate users who have logged out, potentially accessing sensitive business data, performing unauthorized transactions, or manipulating storefront configurations. This compromises confidentiality and integrity of user sessions and data. Although availability is not affected, the breach of session security can lead to financial losses, reputational damage, and regulatory compliance issues for organizations. The vulnerability is particularly concerning for enterprises relying on Optimizely for B2B commerce, as attackers could leverage this flaw to escalate privileges or move laterally within the network. Given the network-based attack vector and low complexity, exploitation could be automated or integrated into phishing campaigns, increasing the risk of widespread compromise if unmitigated.

Summary

CVE-2025-22386 is a vulnerability classified under CWE-613 (Insufficient Session Expiration) affecting Optimizely Configured Commerce versions prior to 5.2.2408. The vulnerability resides in the Commerce B2B application’s session management system, where session tokens remain valid even after a user logs out. This improper session invalidation allows an attacker who obtains or intercepts such tokens to reuse them to impersonate the logged-out user, thereby gaining unauthorized access to sensitive storefront functions. The CVSS 3.1 base score of 7.3 reflects the network attack vector (AV:N), low attack complexity (AC:L), requiring privileges (PR:L) and user interaction (UI:R), with high impact on confidentiality and integrity (C:H/I:H) but no impact on availability (A:N). The vulnerability does not require elevated privileges beyond those of a logged-in user but does require user interaction, such as tricking a user into logging out or session token exposure. No public exploits have been reported yet, but the risk remains significant due to the potential for session hijacking and unauthorized transactions or data access. The lack of a patch link indicates that a fix may be pending or not yet publicly released. This vulnerability highlights the critical need for robust session management controls in web commerce platforms to prevent session reuse after logout.

CWE-613Insufficient Session Expiration (opens in a new tab)
Base weaknessOWASP Top 10 A07:2025: Authentication Failures (opens in a new tab)
According to WASC, "Insufficient Session Expiration is when a web site permits an attacker to reuse old session credentials or session IDs for authorization."
Implementation
Set sessions/credentials expiration date.
OWASP Cheat Sheets
OWASP Authentication (opens in a new tab)
OWASP ASVS 4.0.3
V2.8.1 (opens in a new tab)
V2.8.6 (opens in a new tab)
V3.6.1 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

support.optimizely.com/hc/en-us/articles/32695284701069-Configured-Commerce-Security-Advisory-COM-2024-04 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 25 Feb 2026, 22:12 UTC

WeaknessesCWE-613

Technical details

References

Community reviews

Related threats