CVE-2023-1623: Custom Post Type UI < 1.13.5 - Debug Info Sending via CSRF
First published: Mon Apr 24 2023(Updated: )
The Custom Post Type UI WordPress plugin before 1.13.5 does not properly check for CSRF when sending the debug information to a user supplied email, which could allow attackers to make a logged in admin send such information to an arbitrary email address via a CSRF attack.
Credit: contact@wpscan.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Webdevstudios Custom Post Type Ui | <1.13.5 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Frequently Asked Questions
What is the severity of CVE-2023-1623?
The severity of CVE-2023-1623 is considered medium due to its potential for exploitation through CSRF attacks.
How do I fix CVE-2023-1623?
To fix CVE-2023-1623, update the Custom Post Type UI plugin to version 1.13.5 or later.
What does CVE-2023-1623 exploit?
CVE-2023-1623 exploits a failure to properly check for CSRF, allowing attackers to send debug information to arbitrary email addresses.
Who is affected by CVE-2023-1623?
Users of the Custom Post Type UI WordPress plugin prior to version 1.13.5 are affected by CVE-2023-1623.
What type of attack is associated with CVE-2023-1623?
CVE-2023-1623 is associated with Cross-Site Request Forgery (CSRF) attacks.
- collector/nvd-index
- agent/type
- agent/softwarecombine
- agent/references
- agent/author
- agent/title
- agent/severity
- agent/weakness
- agent/description
- agent/first-publish-date
- agent/event
- agent/source
- agent/tags
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- collector/nvd-api
- source/NVD
- agent/software-canonical-lookup
- vendor/webdevstudios
- canonical/webdevstudios custom post type ui