> For the complete documentation index, see [llms.txt](https://appsecexplained.gitbook.io/appsecexplained/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://appsecexplained.gitbook.io/appsecexplained/common-vulns/vulnerable-components.md).

# Vulnerable components

## What is it?

Pentesting vulnerable components in web applications refers to the process of identifying, analyzing, and testing potential weaknesses present in various components of a web application, such as libraries, frameworks, and other software modules.

**A simple example** 

A web application may use an outdated version of jQuery, which is known to have vulnerabilities. If an attacker can exploit this vulnerability, they may be able to run arbitrary code on a user's browser, potentially leading to unauthorized access or data theft.

**Other learning resources:**

* OWASP Top 10: <https://owasp.org/www-project-top-ten/>
* CWE/SANS Top 25: <https://www.sans.org/top25-software-errors/>
* Web Application Security Testing Cheat Sheet: <https://cheatsheetseries.owasp.org/cheatsheets/Web_Application_Security_Testing_Cheat_Sheet.html>

## Checklist

* [ ] What components exist?
  * [ ] What does the technology stack look like? (libraries, frameworks, etc.)
  * [ ] Identify all plugins and extensions used
    * [ ] Is it a CMS with plugins?
  * [ ] Identify the versions of all these components
* [ ] Are there known vulnerabilities for those components?
  * [ ] NVD, exploit-db, dependency checker, etc
* [ ] Do the exploits have PoCs or available exploits?
* [ ] Can we validate the vulnerability?
  * [ ] If not, what other protections need to be bypassed?


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://appsecexplained.gitbook.io/appsecexplained/common-vulns/vulnerable-components.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.