# Possible expression language (EL) injection detected

## Overview

* **Rule ID**: `java_lang_expression_language_injection`
* **Applicable Languages**: Java
* **Weakness ID**: CWE-917

## Description

Expression Language (EL) injection vulnerabilities arise when unvalidated external input is incorporated into EL statements. This can lead to the inadvertent execution of malicious code.

## Remediation Guidelines

* **Always validate** all external input or dynamic values before incorporating them into EL statements. This is essential to mitigate the risk of EL injection attacks.

## References

* [**OWASP Expression Language Injection**](https://owasp.org/www-community/vulnerabilities/Expression_Language_Injection)
* [**CWE-917: Improper Neutralization of Special Elements used in an Expression Language Statement ('Expression Language Injection')**](https://cwe.mitre.org/data/definitions/917.html)
* [**OWASP Top 10: A03:2021 - Injection**](https://owasp.org/Top10/A03_2021-Injection/)

## Configuration

To omit this rule during a scan, and to provide you with continuous 24/7 code-level scanning, you can employ our [**SAST TOOL**](https://scopy.sec1.io/login)


---

# Agent Instructions: 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:

```
GET https://docs.sec1.io/user-docs/4-sast/2-java/possible-expression-language-el-injection-detected.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.