HomeWordPress vulnerabilitiesCustom 404 Pro
Custom 404 Pro vulnerabilities
Custom 404 Pro has 6 known vulnerabilities in this database. The most recent published record is dated 11 Oct 2025.
- Known vulnerabilities
- 6
- Active installs
- 7,000+
- Latest version
- 3.16.0
- Last updated
- 30 Aug 2026
- Most recent
- 11 Oct 2025
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| SQL injection CVE-2025-9947 | Medium 4.9 | Up to 3.12.0 | Fixed in a later version (latest 3.16.0) | 11 Oct 2025 |
| SQL injection CVE-2023-2032 | Critical 9.8 | Before 3.8.1 | Fixed in 3.8.1 | 27 Jun 2023 |
| Cross-site scripting (XSS) CVE-2023-2023 | Medium 6.1 | Before 3.7.3 | Fixed in 3.7.3 | 30 May 2023 |
| Cross-site request forgery (CSRF) CVE-2023-0385 | Medium 4.3 | Before 3.7.2 | Fixed in 3.7.2 | 18 Jan 2023 |
| Cross-site scripting (XSS) CVE-2019-15838 | Medium 6.1 | Before 3.2.8 | Fixed in 3.2.8 | 30 Aug 2019 |
| Cross-site scripting (XSS) CVE-2019-14789 | Medium 6.1 | Not yet published | Check for an update | 15 Aug 2019 |
Read the published descriptions
- CVE-2025-9947, 11 Oct 2025
- The Custom 404 Pro plugin for WordPress is vulnerable to time-based SQL Injection via the ‘path’ parameter in all versions up to, and including, 3.12.0 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with Administrator-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. CVE record
- CVE-2023-2032, 27 Jun 2023
- The Custom 404 Pro WordPress plugin before 3.8.1 does not properly sanitize database inputs, leading to multiple SQL Injection vulnerabilities. CVE record
- CVE-2023-2023, 30 May 2023
- The Custom 404 Pro WordPress plugin before 3.7.3 does not escape some URLs before outputting them in attributes, leading to Reflected Cross-Site Scripting. CVE record
- CVE-2023-0385, 18 Jan 2023
- The Custom 404 Pro plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 3.7.1. This is due to missing or incorrect nonce validation on the custom_404_pro_admin_init function. This makes it possible for unauthenticated attackers to delete logs, via forged request granted they can trick a site administrator into performing an action such as clicking on a link. CVE record
- CVE-2019-15838, 30 Aug 2019
- The custom-404-pro plugin before 3.2.8 for WordPress has reflected XSS, a different vulnerability than CVE-2019-14789. CVE record
- CVE-2019-14789, 15 Aug 2019
- The Custom 404 Pro plugin 3.2.8 for WordPress has XSS via the wp-admin/admin.php?page=c4p-main page parameter. CVE record
What to do if you run Custom 404 Pro
If you run Custom 404 Pro, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new Custom 404 Pro vulnerabilities
Free. We email you when a new vulnerability is published for Custom 404 Pro, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.