Custom 404 Pro at a glance
- 12 publicly disclosed vulnerabilities, 4 of them rated High or Critical. The most recent was disclosed on Oct 10, 2025.
- Ranked #2633 by popularity on WordPress.org (7,000+ active installs).
- The latest version is 3.16.0 (released Aug 30, 2026). The most recent security fix shipped in 3.12.1.
- Every disclosed vulnerability has a fix. If you are on the latest version, none of them apply to you.
- The first thing to do: update to the latest version and turn on automatic updates.
Check your Custom 404 Pro version
Enter the Custom 404 Pro version number shown on your Plugins screen to see only the vulnerabilities that apply to it, most serious first.
Your version number is compared on this page only. It is not sent anywhere.
Get an email when a new vulnerability is disclosed
We'll tell you when a new vulnerability is disclosed in “Custom 404 Pro”, with the version that fixes it. Free, email address only, stop any time.
We use your email address only for these alerts. Privacy policy
Want every plugin and theme on your site checked daily?
With Security Ready Standard, just install the “KazLinks Security Ready” plugin from WordPress.org. It sends only the names and versions of your plugins and themes, and we check them against disclosed vulnerabilities every day. Your first in-depth scan is free.
How to check whether your site is affected
- 1
Find your version
In your WordPress dashboard, open Plugins → Installed Plugins and look at the version number under “Custom 404 Pro”.
- 2
Compare it with the list below
If your version falls within “Affected versions”, that vulnerability applies to you. If you are on the “Fixed in” version or later, it does not.
- 3
Update
Click “Update now” to move to the latest version (3.16.0). Taking a backup first is a good idea.
- 4
Turn on automatic updates
On the same screen, click “Enable auto-updates” so future fixes are installed automatically.
Known Custom 404 Pro vulnerabilities
Custom 404 Pro <= 3.12.0 - Authenticated (Administrator+) SQL Injection via `path` Parameter
SQL injection · CVE-2025-9947
Affected versions: ≤ 3.12.0
Fixed in: 3.12.1
Severity: Medium 4.9 · Disclosed Oct 10, 2025
Custom 404 Pro <= 3.12.0 - Cross-Site Request Forgery
Cross-site request forgery (CSRF) · CVE-2025-62880
Affected versions: ≤ 3.12.0
Fixed in: 3.12.1
Severity: Medium 4.3 · Disclosed May 13, 2025
Custom 404 Pro <= 3.11.1 - Reflected Cross-Site Scripting
Cross-site scripting (XSS) · CVE-2024-39646
Affected versions: ≤ 3.11.1
Fixed in: 3.11.2
Severity: Medium 6.1 · Disclosed Aug 1, 2024
Custom 404 Pro <= 3.10.0 - Unauthenticated Stored Cross-Site Scripting via logging
Cross-site scripting (XSS) · CVE-2023-51540
Affected versions: ≤ 3.10.0
Fixed in: 3.10.1
Severity: High 7.2 · Disclosed Dec 27, 2023
Custom 404 Pro <= 3.8.1 - Reflected Cross-Site Scripting via 'page'
Cross-site scripting (XSS) · CVE-2023-32740
Affected versions: ≤ 3.8.1
Fixed in: 3.8.2
Severity: Medium 6.1 · Disclosed May 15, 2023
Custom 404 Pro <= 3.7.2 - Reflected Cross-Site Scripting via 's'
Cross-site scripting (XSS) · CVE-2023-2023
Affected versions: ≤ 3.7.2
Fixed in: 3.7.3
Severity: Medium 6.1 · Disclosed May 2, 2023
Custom 404 Pro <= 3.8.0 - Unauthenticated SQL Injection via 's'
SQL injection · CVE-2023-2032
Affected versions: ≤ 3.8.0
Fixed in: 3.8.1
Severity: Critical 9.8 · Disclosed Apr 25, 2023
Custom 404 Pro <= 3.7.2 - Unauthenticated SQL Injection
SQL injection
Affected versions: < 3.7.3
Fixed in: 3.7.3
Severity: Critical 9.8 · Disclosed Apr 25, 2023
Custom 404 Pro <= 3.7.1 - Cross-Site Request Forgery
Cross-site request forgery (CSRF) · CVE-2023-0385
Affected versions: ≤ 3.7.1
Fixed in: 3.7.2
Severity: Medium 4.3 · Disclosed Jan 18, 2023
Custom 404 Pro <= 3.7.0 - Authenticated (Administrator+) SQL Injection
SQL injection · CVE-2022-47605
Affected versions: ≤ 3.7.0
Fixed in: 3.7.1
Severity: High 7.2 · Disclosed Jan 13, 2023
Custom 404 Pro <= 3.2.8 - Reflected Cross-Site Scripting
Cross-site scripting (XSS) · CVE-2019-14789
Affected versions: < 3.2.9
Fixed in: 3.2.9
Severity: Medium 6.1 · Disclosed Jun 25, 2019
Custom 404 Pro <= 3.2.7 - Reflected Cross-Site Scripting
Cross-site scripting (XSS) · CVE-2019-15838
Affected versions: < 3.2.8
Fixed in: 3.2.8
Severity: Medium 6.1 · Disclosed Jun 24, 2019
| Vulnerability | Affected versions | Fixed in | Severity | Disclosed |
|---|---|---|---|---|
| Custom 404 Pro <= 3.12.0 - Authenticated (Administrator+) SQL Injection via `path` ParameterSQL injection · CVE-2025-9947 | ≤ 3.12.0 | 3.12.1 | Medium 4.9 | Oct 10, 2025 |
| Custom 404 Pro <= 3.12.0 - Cross-Site Request ForgeryCross-site request forgery (CSRF) · CVE-2025-62880 | ≤ 3.12.0 | 3.12.1 | Medium 4.3 | May 13, 2025 |
| Custom 404 Pro <= 3.11.1 - Reflected Cross-Site ScriptingCross-site scripting (XSS) · CVE-2024-39646 | ≤ 3.11.1 | 3.11.2 | Medium 6.1 | Aug 1, 2024 |
| Custom 404 Pro <= 3.10.0 - Unauthenticated Stored Cross-Site Scripting via loggingCross-site scripting (XSS) · CVE-2023-51540 | ≤ 3.10.0 | 3.10.1 | High 7.2 | Dec 27, 2023 |
| Custom 404 Pro <= 3.8.1 - Reflected Cross-Site Scripting via 'page'Cross-site scripting (XSS) · CVE-2023-32740 | ≤ 3.8.1 | 3.8.2 | Medium 6.1 | May 15, 2023 |
| Custom 404 Pro <= 3.7.2 - Reflected Cross-Site Scripting via 's'Cross-site scripting (XSS) · CVE-2023-2023 | ≤ 3.7.2 | 3.7.3 | Medium 6.1 | May 2, 2023 |
| Custom 404 Pro <= 3.8.0 - Unauthenticated SQL Injection via 's'SQL injection · CVE-2023-2032 | ≤ 3.8.0 | 3.8.1 | Critical 9.8 | Apr 25, 2023 |
| Custom 404 Pro <= 3.7.2 - Unauthenticated SQL InjectionSQL injection | < 3.7.3 | 3.7.3 | Critical 9.8 | Apr 25, 2023 |
| Custom 404 Pro <= 3.7.1 - Cross-Site Request ForgeryCross-site request forgery (CSRF) · CVE-2023-0385 | ≤ 3.7.1 | 3.7.2 | Medium 4.3 | Jan 18, 2023 |
| Custom 404 Pro <= 3.7.0 - Authenticated (Administrator+) SQL InjectionSQL injection · CVE-2022-47605 | ≤ 3.7.0 | 3.7.1 | High 7.2 | Jan 13, 2023 |
| Custom 404 Pro <= 3.2.8 - Reflected Cross-Site ScriptingCross-site scripting (XSS) · CVE-2019-14789 | < 3.2.9 | 3.2.9 | Medium 6.1 | Jun 25, 2019 |
| Custom 404 Pro <= 3.2.7 - Reflected Cross-Site ScriptingCross-site scripting (XSS) · CVE-2019-15838 | < 3.2.8 | 3.2.8 | Medium 6.1 | Jun 24, 2019 |
Vulnerability data: Wordfence Intelligence (Copyright Defiant, Inc. · license terms). Severity is the CVSS score (0–10). Most recent disclosure: Oct 10, 2025.
Most common weaknesses in Custom 404 Pro
Cross-site scripting (XSS)
6 issues
An attacker plants a malicious script on a page so that it runs in visitors’ browsers. If an administrator opens that page, the attacker can steal their session or act as the administrator.
SQL injection
4 issues
Input such as a form field can be used to rewrite the queries the site sends to its database. Attackers use it to pull out customer, member or order data.
Cross-site request forgery (CSRF)
2 issues
If an administrator who is logged in opens a booby-trapped page elsewhere, the site can be made to change settings without their knowledge.
Frequently asked questions
Is Custom 404 Pro safe to use?
Custom 404 Pro is a well-known plugin with 7,000+ active installs. Finding vulnerabilities in popular plugins is common, and most of them are fixed in newer versions. The important thing is to stay on the latest version (3.16.0) and turn on automatic updates.
How do I find which version of Custom 404 Pro my site is running?
In your WordPress dashboard, go to Plugins → Installed Plugins. The version number is shown under the plugin name. If you see “There is a new version available”, you are on an older version.
Could updating break my site?
Occasionally an update changes how something looks or works, so take a backup before updating. If an agency or developer maintains your site, send them a link to this page and ask them to update.
Can I check all my other plugins too?
Yes. Security Ready reads the versions of every plugin and theme on your site, matches them against known vulnerabilities every day, and tells you what to fix. Your first in-depth scan is free.
Check every plugin and theme automatically, every day
Security Ready reads the versions of every plugin, theme and WordPress core on your site, matches them against known vulnerabilities every day, and tells you how to fix what it finds. Your first in-depth scan is free, and no payment details are needed.
Think your site has already been hacked? Before updating, read what to do in the first hour. Updating alone does not remove a backdoor that has already been planted.