Skip to content

Product

Optimizely configured commerce vulnerabilities

8 published CVES affecting Optimizely configured commerce, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).

Total
8
Critical
0
High
4
Medium
4
Low
0
Unscored
0
CISA KEV
0

Latest Optimizely configured commerce CVEs

Newest publication first

  1. MediumCVSS 4.6 EPSS 0.23%

    An issue was discovered in Optimizely Configured Commerce before 5.2.2408. A medium-severity input validation issue exists in the Commerce B2B application, affecting the Contact Us functionality. This allows visitors to send e-mail messages that could contain unfiltered HTML mark...

  2. MediumCVSS 5.9 EPSS 0.33%

    An issue was discovered in Optimizely Configured Commerce before 5.2.2408. For newly created accounts, the Commerce B2B application does not require email confirmation. This medium-severity issue allows the mass creation of accounts. This could affect database storage; also, non-...

  3. HighCVSS 7.5 EPSS 0.42%

    An issue was discovered in Optimizely Configured Commerce before 5.2.2408. A medium-severity issue concerning business logic exists in the Commerce B2B application, which allows storefront visitors to purchase discontinued products in specific scenarios where requests are altered...

  4. HighCVSS 7.5 EPSS 0.38%

    An issue was discovered in Optimizely Configured Commerce before 5.2.2408. A medium-severity issue exists in requests for resources where the session token is submitted as a URL parameter. This exposes information about the authenticated session, which can be leveraged for sessio...

  5. HighCVSS 7.3 EPSS 0.29%

    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 acti...

Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.