Skip to content

Commit 4cc5da1

Browse files
committed
minor #18897 [ExpressionLanguage] Reword the explanation about external injections (javiereguiluz)
This PR was squashed before being merged into the 5.4 branch. Discussion ---------- [ExpressionLanguage] Reword the explanation about external injections Fixes #17978. Commits ------- 0f169f3 [ExpressionLanguage] Reword the explanation about external injections
2 parents ef1a001 + 0f169f3 commit 4cc5da1

File tree

1 file changed

+6
-5
lines changed

1 file changed

+6
-5
lines changed

components/expression_language.rst

Lines changed: 6 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -22,8 +22,8 @@ How can the Expression Language Help Me?
2222
----------------------------------------
2323

2424
The purpose of the component is to allow users to use expressions inside
25-
configuration for more complex logic. For some examples, the Symfony Framework
26-
uses expressions in security, for validation rules and in route matching.
25+
configuration for more complex logic. For example, the Symfony Framework uses
26+
expressions in security, for validation rules and in route matching.
2727

2828
Besides using the component in the framework itself, the ExpressionLanguage
2929
component is a perfect candidate for the foundation of a *business rule engine*.
@@ -43,9 +43,10 @@ way without using PHP and without introducing security problems:
4343
# Send an alert when
4444
product.stock < 15
4545
46-
Expressions can be seen as a very restricted PHP sandbox and are immune to
47-
external injections as you must explicitly declare which variables are available
48-
in an expression.
46+
Expressions can be seen as a very restricted PHP sandbox and are less vulnerable
47+
to external injections because you must explicitly declare which variables are
48+
available in an expression (but you should still sanitize any data given by end
49+
users and passed to expressions).
4950

5051
Usage
5152
-----

0 commit comments

Comments
 (0)