Security readout for executives and security teams
Plain-English summary
Custom 404 Pro for WordPress had an admin-side request protection flaw through version 3.7.1. If an attacker tricks a logged-in site administrator into clicking a crafted link, plugin logs could be deleted. The cited impact is limited to log integrity, not data theft or site takeover.
Executive priority
Treat this as a moderate-priority hygiene issue. It does not indicate direct site compromise, but it can erase operational evidence and should be addressed during routine WordPress maintenance, faster on sites where 404 logs support security monitoring or compliance review.
Technical view
CVE-2023-0385 is CWE-352 CSRF in Custom 404 Pro’s custom_404_pro_admin_init function due to missing or incorrect nonce validation. The CVSS 3.1 score is 4.3, requiring network access and administrator interaction, with low integrity impact and no cited confidentiality or availability impact.
Likely exposure
Exposure is limited to WordPress sites running Custom 404 Pro versions up to and including 3.7.1. Sites not using this plugin, or using versions outside the affected range, are not indicated as affected by the supplied sources.
Exploitation context
The source bundle does not identify active exploitation, and KEV status is false. Abuse requires social engineering a logged-in administrator into performing an action such as clicking a link. The documented result is deletion of plugin logs, not code execution or privilege escalation.
Researcher notes
The public evidence ties the issue to missing or incorrect nonce validation in AdminClass.php and describes log deletion via CSRF. The supplied data does not provide a fixed version, proof of exploitation, or broader impact beyond plugin log deletion.
Mitigation direction
- Inventory WordPress sites for Custom 404 Pro and record installed versions.
- Update according to vendor or WordPress plugin guidance if a fixed release is available.
- Disable or remove the plugin where no trusted fixed version can be confirmed.
- Limit administrator exposure to untrusted links while logged into WordPress.
- Preserve relevant 404 logs externally if they support investigations or operations.
Validation and detection
- Confirm whether each WordPress site has Custom 404 Pro installed.
- Verify whether installed versions are 3.7.1 or earlier.
- Review installed plugin code for nonce validation around custom_404_pro_admin_init.
- Check vendor or plugin repository guidance for fixed-version information.
- Review administrative log deletion events for unexplained or suspicious timing.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-352: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2023-0385 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 4.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N2.81.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
4.3MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://www.wordfence.com/threat-intel/vulnerabilities/id/968920b9-febf-4d76-a16b-f27954cd72e5?source=cveCVE reference
- https://plugins.trac.wordpress.org/browser/custom-404-pro/tags/3.7.1/admin/AdminClass.php#L114CVE reference
- https://www.wordfence.com/threat-intel/vulnerabilities/id/968920b9-febf-4d76-a16b-f27954cd72e5CVE reference · x_transferred
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Cross-Site Request Forgery (CSRF)
Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.