JSM Show Post Metadata < 4.9.1 - Contributor+ Stored XSS via Custom Field Meta Key
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Unknown | JSM Show Post Metadata | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Wordpress-extensions | Jsm Show Post Metadata |
|
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.431% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Wordpress-extensions
Wordpress-extensions jsm Show Post Metadata |
|
| Vendors & Products |
Wordpress-extensions
Wordpress-extensions jsm Show Post Metadata |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | The JSM Show Post Metadata WordPress plugin before 4.9.1 does not properly escape a post meta key before outputting it into an inline event-handler attribute in an admin-facing meta box, allowing users with contributor-level access and above to inject arbitrary JavaScript that executes in the session of a higher-privileged user who reviews the affected post. | |
| Title | JSM Show Post Metadata < 4.9.1 - Contributor+ Stored XSS via Custom Field Meta Key | |
| Weaknesses | CWE-79 | |
| References |
| |
| Metrics |
cvssV3_1
|