CVE-2025-22385: Missing Authorization
Source CVE Database V5
Not known to be exploited · CVSS 5.9 Medium · fixed in 5.2.2408 : update Optimizely Configured Commerce when convenient.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 25% 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:H/PR:N/UI:N/S:U/C:N/I:N/A:HExploitation 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 2026-10-25.
What to do
AI-suggested
Organizations should upgrade Optimizely Configured Commerce to version 5.2.2408 or later, where this issue is resolved. Until patching is possible, implement rate limiting and CAPTCHA challenges on account creation endpoints to mitigate automated mass account creation. Monitor account creation logs for unusual spikes or patterns indicative of abuse. Employ web application firewalls (WAFs) with rules targeting suspicious account creation behaviors. Review and tighten account verification processes, potentially adding manual or secondary verification steps. Regularly audit database storage and account inventories to detect and remove unauthorized or suspicious accounts. Coordinate with Optimizely support for any available interim fixes or guidance. Educate operational teams to recognize symptoms of exploitation and respond promptly.
Description
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 accounts can be created on behalf of visitors.