PostX < 5.0.41 - Unauthenticated Custom Field Key Disclosure via REST API
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 | Post Grid Gutenberg Blocks | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Wordpress-extensions | Postx |
|
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.345% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Wordpress-extensions
Wordpress-extensions postx |
|
| Vendors & Products |
Wordpress-extensions
Wordpress-extensions postx |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | The Post Grid Gutenberg Blocks WordPress plugin before 5.0.41 does not perform an authorization or post-visibility check on a REST API route that returns the custom field keys of a given post, allowing unauthenticated users to disclose the custom field key names of arbitrary posts, including private, draft, pending, scheduled and password-protected posts. | |
| Title | PostX < 5.0.41 - Unauthenticated Custom Field Key Disclosure via REST API | |
| Weaknesses | CWE-200 | |
| References |
| |
| Metrics |
cvssV3_1
|