> For the complete documentation index, see [llms.txt](https://hacking-notes.jord4n.pro/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hacking-notes.jord4n.pro/web/nosql-injection/detection-of-nosql-injection.md).
# Detection of NoSQL Injection
Detection of NoSQL Injection notes for PortSwigger Web Security Academy labs, including exploitation workflow, payload testing, Burp Suite validation, and remediation context.
### Detecting NoSQL Injection
**Lab objective**
This lab contains an e-commerce application whose category filter is based on a database **MongoDB (NoSQL)**. / A NoSQL injection vulnerability allows you to display **unpublished products**.
The aim is to exploit this vulnerability in order to force the application to return all products, including those that should not be visible.
**Application Context**
* e-commerce page with one filter by category.
* Example of normal request
```bash
filter?category=Accessories
```
**Vulnerability identification**
When adding a **apostrophe** at the end of the `category` parameter, the server returns an internal error:
```bash
Internal Server Error
Command failed with error 139 (JSInterpreterFailure):
SyntaxError: unterminated string literal....
```
This error reveals several important elements:
* Backend uses **MongoDB**.
* User entries are interpreted in a **JavaScript** context on the database side.
* The application is vulnerable to \*\* NoSQL\*\* injection.
**NoSQL Injection Exploitation**
The objective is to manipulate the condition used in the MongoDB request so that it is always true.
Examples of tested payloads:
```sql
' || 1==1 || '
' || true || '
' && 0 && '
```
These expressions force the condition to be true, which causes the display of \*\* all products\*\* including those not published
#### Non-functional Payloads (for Comparison)
```sql
' && 0 && '
' || 1==2 || '
```
These conditions are assessed as false and do not return any products
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://hacking-notes.jord4n.pro/web/nosql-injection/detection-of-nosql-injection.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
