← WordPress Vulnerabilities
WordPress security by component

Custom 404 Pro

Custom 404 Pro is a WordPress component with 11 published CVE records in this archive. The latest tracked vulnerability was published Dec 22, 2025; the highest CVE/CNA score is 9.8.

Plugin slug: custom-404-pro

CVE-2025-62880: Custom 404 Pro: Cross-site request forgery

Custom 404 Pro is affected by cross-site request forgery. Exposure depends on how the affected operation is made reachable by the site. Exploitation relies on a signed-in privileged user submitting an attacker-controlled request.

PublishedDec 22, 2025
Safe version guidanceSee mitigation notes
Safe version
Dec 22, 2025 CVE-2025-62880
Custom 404 Pro: Cross-site request forgery
Custom 404 Pro is affected by cross-site request forgery. Exposure depends on how the affected operation is made reachable by the site. Exploitation relies on a signed-in privileged user submitting an attacker-controlled request.
See mitigation notes
CVE4.3
NVDPending
Oct 11, 2025 CVE-2025-9947
Custom 404 Pro: SQL injection
Custom 404 Pro is affected by SQL injection. Exploitation requires at least administrator-level access. A successful request can alter database queries and expose or modify WordPress data.
See mitigation notes
CVE4.9
NVDPending
Aug 01, 2024 CVE-2024-39646
Custom 404 Pro: Cross-site scripting
Custom 404 Pro is affected by cross-site scripting. Exposure depends on how the affected operation is made reachable by the site. Injected script can execute in the affected site's origin when the vulnerable output is viewed.
See mitigation notes
CVE7.1
NVD6.1
Feb 01, 2024 CVE-2023-51540
Custom 404 Pro: Cross-site scripting
Custom 404 Pro is affected by cross-site scripting. Exposure depends on how the affected operation is made reachable by the site. Injected script can execute in the affected site's origin when the vulnerable output is viewed.
See mitigation notes
CVE7.1
NVD6.1
Aug 30, 2023 CVE-2023-32740
Custom 404 Pro: Cross-site scripting
Custom 404 Pro is affected by cross-site scripting. Exposure depends on how the affected operation is made reachable by the site. Injected script can execute in the affected site's origin when the vulnerable output is viewed.
See mitigation notes
CVE5.8
NVD6.1
Jun 27, 2023 CVE-2023-2032
Custom 404 Pro: SQL injection
Custom 404 Pro is affected by SQL injection. Exposure depends on how the affected operation is made reachable by the site. A successful request can alter database queries and expose or modify WordPress data.
See mitigation notes
CVE9.8
NVD9.8
May 30, 2023 CVE-2023-2023
Custom 404 Pro: Cross-site scripting
Custom 404 Pro is affected by cross-site scripting. Exposure depends on how the affected operation is made reachable by the site. Injected script can execute in the affected site's origin when the vulnerable output is viewed.
See mitigation notes
CVE6.1
NVD6.1
Apr 12, 2023 CVE-2022-47605
Custom 404 Pro: SQL injection
Custom 404 Pro is affected by SQL injection. Exposure depends on how the affected operation is made reachable by the site. A successful request can alter database queries and expose or modify WordPress data.
See mitigation notes
CVE6.4
NVD7.2
Jan 18, 2023 CVE-2023-0385
Custom 404 Pro: Cross-site request forgery
Custom 404 Pro is affected by cross-site request forgery. The vulnerable path is reachable without authentication. Exploitation relies on a signed-in privileged user submitting an attacker-controlled request.
See mitigation notes
CVE4.3
NVD4.3
Aug 30, 2019 CVE-2019-15838
Custom 404 Pro: Cross-site scripting
Custom 404 Pro is affected by cross-site scripting. Exposure depends on how the affected operation is made reachable by the site. Injected script can execute in the affected site's origin when the vulnerable output is viewed.
See mitigation notes
CVE6.1
NVD6.1
Aug 15, 2019 CVE-2019-14789
Custom 404 Pro: Cross-site scripting
Custom 404 Pro is affected by cross-site scripting. Exposure depends on how the affected operation is made reachable by the site. Injected script can execute in the affected site's origin when the vulnerable output is viewed.
See mitigation notes
CVE6.1
NVD6.1