CVE-2025-40675
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 · uneditedA Reflected Cross-Site Scripting (XSS) vulnerability has been found in Bagisto v2.0.0. This vulnerability allows an attacker to execute JavaScript code in the victim's browser by sending the victim a malicious URL using the parameter 'query' in '/search'. This vulnerability can be exploited to steal sensitive user data, such as session cookies, or to perform actions on behalf of the user.
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 · moderate confidenceReflected XSS vulnerability in Bagisto v2.0.0 allows injection of malicious JavaScript via the 'query' parameter in the /search endpoint. The attacker crafts a URL containing JavaScript code that executes in the victim's browser when they click the malicious link, enabling session cookie theft and unauthorized actions.
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>= 2.0.0, < 2.2.3CVSS 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
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
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 Bagisto versionLocate the composer.json file in the Bagisto root directory and read the 'version' field, or run 'composer show webkul/bagisto' to display installed package version information.Affected if The installed version is >= 2.0.0 and < 2.2.3.
-
Verify the /search endpoint existsCheck your application's route configuration files (typically in routes/web.php or routes/admin.php) for a route definition matching the /search path pattern.Affected if A route handling /search is defined and accessible.
-
Confirm the 'query' parameter acceptanceInspect the controller method handling the /search route to verify it accepts a 'query' parameter for processing search terms.Affected if The search controller reads and processes the 'query' parameter without apparent sanitization.
-
Test for reflected XSS in the query parameterSubmit a harmless test payload such as '<script>alert(1)</script>' as the query parameter value to the /search endpoint and inspect whether the payload is reflected unescaped in the response HTML.Affected if The submitted payload appears literally in the HTML response without HTML entity encoding.
You are affected if your Bagisto installation version falls within 2.0.0 through 2.2.2 and the /search endpoint reflects the query parameter unescaped in its response.
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 · scoped2.2.3
Implement strict input validation and sanitization on the 'query' parameter, combined with proper output encoding when rendering search results. Additionally, configure Content Security Policy (CSP) headers to mitigate XSS execution.
Bagisto version 2.2.3 or later
- 1. Back up your current Bagisto installation and database before upgrading
- 2. Review the Bagisto upgrade documentation for version 2.2.3
- 3. Run the appropriate upgrade command or manually update to version 2.2.3 or later
- 4. Verify the XSS vulnerability in the '/search' query parameter is no longer present
- 5. Test that the upgrade did not break existing functionality
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-40675 — 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-40675 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