<?xml version="1.0" encoding="UTF-8"?><?xml-stylesheet type="text/xsl" href="../assets/feed.xsl"?><rss version="2.0"><channel><title>PatchTheCVE: configured commerce</title><link>https://patchthecve.com/</link><description>CVEs with upgrade or downgrade fix steps</description><item><title>CVE-2025-22387: An issue was discovered in Optimizely Configured Commerce before 5.2.2408</title><link>https://patchthecve.com/cve/CVE-2025-22387.html</link><guid>https://patchthecve.com/cve/CVE-2025-22387.html</guid><pubDate>Wed, 17 Jun 2026 08:46:57 +0000</pubDate><description>HIGH 7.5: 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 session hijacking.</description></item><item><title>CVE-2025-22386: An issue was discovered in Optimizely Configured Commerce before 5.2.2408</title><link>https://patchthecve.com/cve/CVE-2025-22386.html</link><guid>https://patchthecve.com/cve/CVE-2025-22386.html</guid><pubDate>Wed, 17 Jun 2026 08:46:57 +0000</pubDate><description>HIGH 7.3: 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.</description></item><item><title>CVE-2025-22385: An issue was discovered in Optimizely Configured Commerce before 5.2.2408</title><link>https://patchthecve.com/cve/CVE-2025-22385.html</link><guid>https://patchthecve.com/cve/CVE-2025-22385.html</guid><pubDate>Wed, 17 Jun 2026 08:46:56 +0000</pubDate><description>MEDIUM 5.9: 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-requested storefront</description></item><item><title>CVE-2025-22384: An issue was discovered in Optimizely Configured Commerce before 5.2.2408</title><link>https://patchthecve.com/cve/CVE-2025-22384.html</link><guid>https://patchthecve.com/cve/CVE-2025-22384.html</guid><pubDate>Wed, 17 Jun 2026 08:46:56 +0000</pubDate><description>HIGH 7.5: 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 before reaching the</description></item><item><title>CVE-2025-22383: An issue was discovered in Optimizely Configured Commerce before 5.2.2408</title><link>https://patchthecve.com/cve/CVE-2025-22383.html</link><guid>https://patchthecve.com/cve/CVE-2025-22383.html</guid><pubDate>Wed, 17 Jun 2026 08:46:55 +0000</pubDate><description>MEDIUM 4.6: 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 markup in specific scena</description></item><item><title>CVE-2024-56175: In Optimizely Configured Commerce before 5.2.2408, malicious payloads can be stored and subsequently executed </title><link>https://patchthecve.com/cve/CVE-2024-56175.html</link><guid>https://patchthecve.com/cve/CVE-2024-56175.html</guid><pubDate>Wed, 17 Jun 2026 08:11:47 +0000</pubDate><description>MEDIUM 6.1: In Optimizely Configured Commerce before 5.2.2408, malicious payloads can be stored and subsequently executed in users&#x27; browsers under specific conditions: XSS from client-side template injection in list item names.</description></item><item><title>CVE-2024-56174: In Optimizely Configured Commerce before 5.2.2408, malicious payloads can be stored and subsequently executed </title><link>https://patchthecve.com/cve/CVE-2024-56174.html</link><guid>https://patchthecve.com/cve/CVE-2024-56174.html</guid><pubDate>Wed, 17 Jun 2026 08:11:47 +0000</pubDate><description>HIGH 8.1: In Optimizely Configured Commerce before 5.2.2408, malicious payloads can be stored and subsequently executed in users&#x27; browsers under specific conditions: XSS from client-side template injection in search history.</description></item><item><title>CVE-2024-56173: In Optimizely Configured Commerce before 5.2.2408, malicious payloads can be stored and subsequently executed </title><link>https://patchthecve.com/cve/CVE-2024-56173.html</link><guid>https://patchthecve.com/cve/CVE-2024-56173.html</guid><pubDate>Wed, 17 Jun 2026 08:11:46 +0000</pubDate><description>MEDIUM 4.7: In Optimizely Configured Commerce before 5.2.2408, malicious payloads can be stored and subsequently executed in users&#x27; browsers under specific conditions: XSS from JavaScript in an SVG document.</description></item></channel></rss>