Theme Editor <= 3.1 - Cross-Site Request Forgery to CSS Modification
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| mndpsingh287 | Theme Editor | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Mndpsingh287 | Theme Editor |
|
||||||||
| Wordpress | Wordpress |
|
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.190% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Mndpsingh287
Mndpsingh287 theme Editor Wordpress Wordpress wordpress |
|
| Vendors & Products |
Mndpsingh287
Mndpsingh287 theme Editor Wordpress Wordpress wordpress |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | The Theme Editor plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 3.1. This is due to missing nonce validation on the ms_update AJAX action. This makes it possible for unauthenticated attackers to modify child theme CSS styles via a forged request granted they can trick an administrator into performing an action such as clicking on a link. | |
| Title | Theme Editor <= 3.1 - Cross-Site Request Forgery to CSS Modification | |
| Weaknesses | CWE-352 | |
| References |
|
|
| Metrics |
cvssV3_1
|