CVE-2023-1623

Custom Post Type UI <= 1.13.4 - Cross-Site Request Forgery to Sensitive Information Exposure

2023-03-28 00:00

Strategic Overview

Status: Patched in 1.13.5
Affected Plugin: Custom Post Type UI
Affected Version: <= 1.13.4
CVSS: 5.4Medium
Weakness type: CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
CVE: CVE-2023-1623

View all Custom Post Type UI vulnerabilities

At a glance

CVE-2023-1623 is a medium-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the Custom Post Type UI WordPress plugin, affecting versions <= 1.13.4. It carries a CVSS score of 5.4 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 1.13.5; sites on affected versions should update now. Disclosed March 2023, reported by Erwan LR.

Vulnerability Overview

The Custom Post Type UI for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 1.13.4 . This is due to missing or incorrect nonce validation in the cptui_render_debuginfo_section function. This makes it possible for unauthenticated attackers to exfiltrate debug information gathered by the plugin via a forged request granted they can trick a site administrator into performing an action such as clicking on a link. The information contains a list of installed and activated themes and plugins, version information for PHP, MySQL and Web Server.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site.

CWE-200: Exposure of Sensitive Information to an Unauthorized Actor

Reaching this weakness in Custom Post Type UI <= 1.13.4 takes a caller who can reach the endpoint. Sensitive information exposure means data the application intended to keep internal is returned to a caller who should not be able to see it.

The disclosed data — credentials, tokens, customer records or internal paths — is usually worth more as material for a follow-up attack than as an end in itself. For Custom Post Type UI the fix is 1.13.5: builds <= 1.13.4 are affected, anything from 1.13.5 onward is not.

Remediation

Update to version 1.13.5, or a newer patched version

How does WordSec protect against this?

The fix is the thing that ends this: Custom Post Type UI 1.13.5 closes this, and updating the plugin is the step that ends it.

Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2023-1623 https://www.wordfence.com/threat-intel/vulnerabilities/id/f28afb93-b72a-4a56-994b-144124202147 https://nvd.nist.gov/vuln/detail/CVE-2023-1623

Related records

CVSS Vector

5.4

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N

Base

Attack VectorNetwork
Attack ComplexityLow
Privileges RequiredNone
User InteractionRequired
ScopeUnchanged
ConfidentialityLow
IntegrityLow
AvailabilityNone

This record contains material that is subject to copyright

CVE Usage: MITRE hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Common Vulnerabilities and Exposures (CVE®). Any copy you make for such purposes is authorized provided that you reproduce MITRE's copyright designation and this license in any such copy.

https://www.cve.org/Legal/TermsOfUse

Defiant hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute this software vulnerability information. Any copy of the software vulnerability information you make for such purposes is authorized provided that you include a hyperlink to this vulnerability record and reproduce Defiant's copyright designation and this license in any such copy.

https://www.wordfence.com/wordfence-intelligence-terms-and-conditions/