CVE-2025-22385
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Optimizely Configured Commerce B2B application before version 5.2.2408 lacks email confirmation enforcement for newly created accounts. This allows automated mass account creation without verifying the requester's identity or consent, potentially filling the database with unverified accounts and enabling account takeover via registration with existing email addresses.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 5.2.2408CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the installed version of Optimizely Configured CommerceLocate the version information in the application admin panel under System Settings or About, or check the assemblies/binaries deployed on the server for the Configured Commerce version numberAffected if The installed version is earlier than 5.2.2408
-
Verify email confirmation settings for new account registrationAccess the B2B Commerce admin configuration panel and locate the Account Settings or Registration Settings section. Look for an option labeled 'Require Email Confirmation', 'Verify Email', or similar that controls whether new accounts must confirm their email address before becoming activeAffected if Email confirmation is disabled or not enforced for new account registrations
-
Inspect the account creation workflow configurationReview the website or application configuration files (such as web.config or appsettings.json) for settings related to email verification during registration, or check the Commerce Manager admin interface for registration workflow settingsAffected if The registration workflow does not include an email verification step before account activation
-
Check for unverified accounts in the databaseQuery the user or account table in the database for records where the email verification status is false, unverified, or pending, or where the account was created without a confirmed email addressAffected if There are accounts present in the system that were created without email verification being completed
A user is affected if their Optimizely Configured Commerce version is below 5.2.2408 AND email confirmation is not enforced for new account registrations in their configuration.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped5.2.2408
Enable and enforce email verification (e.g., confirmation link or one-time passcode) for all new account registrations in the B2B Commerce application, and implement rate limiting on account creation endpoints.
5.2.2408 or later
- Identify the current version of Optimizely Configured Commerce in your environment
- Review the Optimizely upgrade documentation for the path to version 5.2.2408
- Create a complete backup of the database and configuration files
- Perform the upgrade to version 5.2.2408 or later following Optimizely's standard upgrade procedures
- After upgrade, verify that email confirmation is now required for newly created B2B accounts
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-22385 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-22385 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data