CVE-2023-36238: Insecure Direct Object Reference (IDOR) in Bagisto

bagisto/bagisto Updated 02 Oct 2025

Summary

13/03/2024
Yes i
Moderate
6.5

CVE-2023-36238: Bagisto vulnerable to Insecure Direct Object Reference (IDOR). Affects bagisto/bagisto versions < 1.3.2. Fixed in 1.3.2. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

Bagisto is an open-source e-commerce platform built on Laravel. It provides a range of features for creating online stores. The vulnerability in Bagisto version 1.5.0 is related to Insecure Direct Object Reference (IDOR). This vulnerability allows an attacker to access sensitive information by manipulating the invoice ID parameter.

Vulnerability Detail

The Insecure Direct Object Reference (IDOR) vulnerability in Bagisto version 1.5.0 enables an attacker to bypass authorization and access sensitive information. By manipulating the invoice ID parameter, an attacker can retrieve confidential data that they are not authorized to access. This can lead to the exposure of customer information, financial data, or other sensitive details. The vulnerability has a moderate severity rating.

How To Fix

Minimum fixed version

1.3.2

This is the first release that contains the fix.

composer require bagisto/bagisto:1.3.2

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

There is no specific workaround mentioned for this vulnerability. However, it is advised to upgrade to the fixed version as soon as possible to mitigate the risk of unauthorized access to sensitive information.

Conclusion

In conclusion, Bagisto version 1.5.0 is vulnerable to an Insecure Direct Object Reference (IDOR) issue. This vulnerability allows unauthorized access to sensitive information by manipulating the invoice ID parameter. To mitigate the risk, it is crucial to upgrade to Bagisto version 1.3.2 or later. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for bagisto/bagisto →

Share this vulnerability

FAQ

Bagisto is an open-source e-commerce platform built on Laravel. It provides a range of features for creating online stores.

Insecure Direct Object Reference (IDOR) is a vulnerability that allows an attacker to bypass authorization and access sensitive information by manipulating object references.

This vulnerability allows an attacker to obtain sensitive information by manipulating the invoice ID parameter. It can lead to the exposure of confidential data, such as customer information and financial details.

To fix this vulnerability, it is recommended to upgrade to Bagisto version 1.3.2 or later. Ensure proper authorization checks and validate user access to sensitive resources.

There is no specific workaround mentioned for this vulnerability. Upgrading to the fixed version is the recommended solution.

Related vulnerabilities

Recent vulnerabilities recorded for bagisto/bagisto.

How To Fix

Minimum fixed version

1.3.2

This is the first release that contains the fix.

composer require bagisto/bagisto:1.3.2

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback