REDAXO before 5.21.3 CSRF Token Bypass via users/users Privilege Escalation
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| redaxo | core | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Redaxo | Core |
|
||||||||||||
| Redaxo | Redaxo |
|
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.135% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Redaxo core
|
|
| Vendors & Products |
Redaxo core
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | REDAXO before 5.21.3 contains a cross-site request forgery vulnerability in the backend user administration page (users/users) because the CSRF token check only runs when the save parameter is set, while the update path triggered by FUNC_UPDATE does not require it. Attackers can lure a logged-in backend user with the users[] permission to a crafted GET link to grant administrator rights, deactivate accounts, or lock out the sole administrator. | |
| Title | REDAXO before 5.21.3 CSRF Token Bypass via users/users Privilege Escalation | |
| First Time appeared |
Redaxo
Redaxo redaxo |
|
| Weaknesses | CWE-352 | |
| CPEs | cpe:2.3:a:redaxo:redaxo:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Redaxo
Redaxo redaxo |
|
| References |
| |
| Metrics |
cvssV3_1
|