Innoshop up to 0.4.1 _ORDER_ID_ shipping_address_id/billing_address_id direct request
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Innoshop up to 0.4.1. It has been rated as problematic. This vulnerability affects unknown code of the file /en/account/orders/_ORDER_ID_. Performing a manipulation of the argument shipping_address_id/billing_address_id results in direct request. This vulnerability is known as CVE-2025-52920. Remote exploitation of the attack is possible. No exploit is available.
Details
A vulnerability, which was classified as problematic, was found in Innoshop up to 0.4.1. This affects an unknown function of the file /en/account/orders/_ORDER_ID_. The manipulation of the argument shipping_address_id/billing_address_id with an unknown input leads to a direct request vulnerability. CWE is classifying the issue as CWE-425. The web application does not adequately enforce appropriate authorization on all restricted URLs, scripts, or files. This is going to have an impact on confidentiality. The summary by CVE is:
Innoshop through 0.4.1 allows Insecure Direct Object Reference (IDOR) at multiple places within the frontend shop. Anyone can create a customer account and easily exploit these. Successful exploitation results in disclosure of the PII of other customers and the deletion of their reviews of products on the website. To be specific, an attacker could view the order details of any order by browsing to /en/account/orders/_ORDER_ID_ or use the address and billing information of other customers by manipulating the shipping_address_id and billing_address_id parameters when making an order (this information is then reflected in the receipt). Additionally, an attacker could delete the reviews of other users by sending a DELETE request to /en/account/reviews/_REVIEW_ID.
It is possible to read the advisory at github.com. This vulnerability is uniquely identified as CVE-2025-52920 since 06/21/2025. The exploitability is told to be easy. It is possible to initiate the attack remotely. Technical details of the vulnerability are known, but there is no available exploit. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 06/23/2025). The attack technique deployed by this issue is T1006 according to MITRE ATT&CK.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2025-18869). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.3
VulDB Base Score: 4.3
VulDB Temp Score: 4.2
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 6.4
CNA Vector (MITRE): 🔒
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: Direct requestCWE: CWE-425
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: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
06/21/2025 CVE reserved06/23/2025 Advisory disclosed
06/23/2025 VulDB entry created
06/23/2025 VulDB entry last update
Sources
Advisory: github.comStatus: Not defined
CVE: CVE-2025-52920 (🔒)
GCVE (CVE): GCVE-0-2025-52920
GCVE (VulDB): GCVE-100-313635
EUVD: 🔒
Entry
Created: 06/23/2025 14:20Updated: 06/23/2025 15:23
Changes: 06/23/2025 14:20 (62), 06/23/2025 15:23 (1)
Complete: 🔍
Cache ID: 216:0C2: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.