Optimizely Configured Commerce up to 5.2.2407 external control of assumed-immutable web parameter
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.1 | $0-$5k | 0.00 |
Summary
A vulnerability identified as problematic has been detected in Optimizely Configured Commerce up to 5.2.2407. The impacted element is an unknown function. Performing a manipulation results in external control of assumed-immutable web parameter. This vulnerability is reported as CVE-2025-22384. The attack is possible to be carried out remotely. No exploit exists. You should upgrade the affected component.
Details
A vulnerability classified as problematic has been found in Optimizely Configured Commerce up to 5.2.2407. This affects some unknown functionality. The manipulation with an unknown input leads to a external control of assumed-immutable web parameter vulnerability. CWE is classifying the issue as CWE-472. The web application does not sufficiently verify inputs that are assumed to be immutable but are actually externally controllable, such as hidden form fields. This is going to have an impact on integrity. The summary by CVE is:
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 server.
It is possible to read the advisory at support.optimizely.com. This vulnerability is uniquely identified as CVE-2025-22384 since 01/04/2025. The exploitability is told to be easy. It is possible to initiate the attack remotely. The technical details are unknown and an exploit is not publicly available.
Upgrading to version 5.2.2408 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2025-2765). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.3VulDB Meta Temp Score: 4.1
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: External control of assumed-immutable web parameterCWE: CWE-472
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Configured Commerce 5.2.2408
Timeline
01/04/2025 🔍01/04/2025 🔍
01/04/2025 🔍
05/27/2025 🔍
Sources
Advisory: support.optimizely.comStatus: Confirmed
CVE: CVE-2025-22384 (🔍)
GCVE (CVE): GCVE-0-2025-22384
GCVE (VulDB): GCVE-100-290187
EUVD: 🔍
Entry
Created: 01/04/2025 04:01Updated: 05/27/2025 03:07
Changes: 01/04/2025 04:01 (53), 05/27/2025 03:07 (1)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.