Account flooding via missing email verification
Published Jan 4, 2025 · Updated Jan 6, 2025
Missing authorization in Optimizely Configured Commerce before 5.2.2408 allows remote attackers to create unverified storefront accounts. The Commerce B2B registration flow persists a new visitor account without requiring completion of the validation link sent to the supplied email address. No authentication or user interaction is required; repeated registrations can consume database storage and create accounts in visitors' names.
Summary
What happened
Missing authorization in Optimizely Configured Commerce before 5.2.2408 allows remote attackers to create unverified storefront accounts. The Commerce B2B registration flow persists a new visitor account without requiring completion of the validation link sent to the supplied email address. No authentication or user interaction is required; repeated registrations can consume database storage and create accounts in visitors' names.
The record
- CVE
- CVE-2025-22385
- Published
- Jan 4, 2025
- Updated
- Jan 6, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-862
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 4, 2025CVE publishedPublication date reported by the CVE source.
- Jan 6, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo