Is Custom 404 Pro safe to use?

Laskyr does not give safety verdicts. No known unpatched vulnerabilities in the latest version (3.16.0). As of 2026-11-04. 11 issues are on record for older versions; version 3.12.1 or newer fixes all of them that state a fix. Keep Custom 404 Pro on the latest version (3.16.0) and remove it if you do not use it.

Which versions of Custom 404 Pro are vulnerable?

Known issues on record (newest first): Cross-site request forgery (CSRF) (3.12.0 and older, fixed in 3.12.1); SQL injection (3.12.0 and older, fixed in 3.12.1); Cross-site scripting (XSS) (3.11.1 and older, fixed in 3.11.2); Stored cross-site scripting (XSS) (3.10.0 and older, fixed in 3.10.1); Reflected cross-site scripting (XSS) (3.8.1 and older, fixed in 3.8.2); SQL injection (older than 3.8.1, fixed in 3.8.1). The full list with sources is on this page.

What is the latest version of Custom 404 Pro?

3.16.0, according to wordpress.org (last updated 2026-08-30). It has 7,000+ active installs.

What should I do if my Custom 404 Pro is out of date?

Take a backup, then update it from Dashboard > Updates (or run wp plugin update custom-404-pro). If you cannot update right away, deactivate it until you can. If you think the site was already attacked, run a free scan at https://laskyr.com/scan.

Plugins · custom-404-pro · data as of 2026-11-04

Is Custom 404 Pro safe? Known vulnerabilities and latest version

Latest version: 3.16.0
Last updated: 2026-08-30
Active installs: 7,000+
Known issues on record: 11
Unpatched in latest: 0
Tested up to WP: 7.1.4 · PHP 7.4+

Take control of every 404 on your site — redirect visitors to a custom page or URL, log what broke, and get notified when it matters. — by Kunal

What to do

Update to the latest version (3.16.0). Anything older than 3.12.1 has at least one known issue listed below. Dashboard → Updates, or Plugins → “update now”.
If you cannot update right away, deactivate it until you can.
Turn on auto-updates for it: Plugins → “Enable auto-updates” on its row.
If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan.

With WP-CLI: wp plugin get custom-404-pro --field=version shows what you run; wp plugin update custom-404-pro updates it.

Check your version

Known vulnerabilities

11 on record, newest first. “Affected” is the version range the source gives; “fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version.

medium 4.3 CVE-2025-62880 · published 2025-12-22

Cross-site request forgery (CSRF) in Custom 404 Pro (3.12.0 and older)

Affected: 3.12.0 and older
Fixed in: 3.12.1 *
Access needed (per CVSS): No login needed; someone on the site has to click a link or open a page
Range from: CVE record (the advisory publisher) · score by Patchstack

Details from the advisory

Cross-Site Request Forgery (CSRF) vulnerability in Kunal Custom 404 Pro custom-404-pro allows Cross Site Request Forgery.This issue affects Custom 404 Pro: from n/a through <= 3.12.0.

NVD CVE-2025-62880 Patchstack advisory

medium 4.9 CVE-2025-9947 · published 2025-10-11

SQL injection in Custom 404 Pro (3.12.0 and older)

Affected: 3.12.0 and older
Fixed in: 3.12.1 *
Access needed (per CVSS): Needs an admin-level account
Range from: CVE record (the advisory publisher) · score by Wordfence

Details from the advisory

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.

NVD CVE-2025-9947 Wordfence advisory Plugin source

medium 6.1 CVE-2024-39646 · published 2024-08-01

Cross-site scripting (XSS) in Custom 404 Pro (3.11.1 and older)

Affected: 3.11.1 and older
Fixed in: 3.11.2
Access needed (per CVSS): No login needed; someone on the site has to click a link or open a page
Range from: CVE record (the advisory publisher) · score by NVD

Details from the advisory

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Kunal Custom 404 Pro custom-404-pro.This issue affects Custom 404 Pro: from n/a through <= 3.11.1.

NVD CVE-2024-39646 Patchstack advisory

medium 6.1 CVE-2023-51540 · published 2024-02-01

Stored cross-site scripting (XSS) in Custom 404 Pro (3.10.0 and older)

Affected: 3.10.0 and older
Fixed in: 3.10.1
Access needed (per CVSS): No login needed; someone on the site has to click a link or open a page
Range from: CVE record (the advisory publisher) · score by NVD

Details from the advisory

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Kunal Nagar Custom 404 Pro allows Stored XSS.This issue affects Custom 404 Pro: from n/a through 3.10.0.

NVD CVE-2023-51540 Patchstack advisory

medium 6.1 CVE-2023-32740 · published 2023-08-30

Reflected cross-site scripting (XSS) in Custom 404 Pro (3.8.1 and older)

Affected: 3.8.1 and older
Fixed in: 3.8.2
Access needed (per CVSS): No login needed; someone on the site has to click a link or open a page
Range from: CVE record (the advisory publisher) · score by NVD

Details from the advisory

Unauth. Reflected Cross-Site Scripting (XSS) vulnerability in Kunal Nagar Custom 404 Pro plugin <= 3.8.1 versions.

NVD CVE-2023-32740 Patchstack advisory

critical 9.8 CVE-2023-2032 · published 2023-06-27

SQL injection in Custom 404 Pro (older than 3.8.1)

Affected: older than 3.8.1
Fixed in: 3.8.1
Access needed (per CVSS): No login needed
Range from: CVE record (the advisory publisher) · score by NVD

Details from the advisory

The Custom 404 Pro WordPress plugin before 3.8.1 does not properly sanitize database inputs, leading to multiple SQL Injection vulnerabilities.

NVD CVE-2023-2032 WPScan advisory

medium 6.1 CVE-2023-2023 · published 2023-05-30

Reflected cross-site scripting (XSS) in Custom 404 Pro (older than 3.7.3)

Affected: older than 3.7.3
Fixed in: 3.7.3
Access needed (per CVSS): No login needed; someone on the site has to click a link or open a page
Range from: CVE record (the advisory publisher) · score by NVD

Details from the advisory

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.

NVD CVE-2023-2023 WPScan advisory

high 7.2 CVE-2022-47605 · published 2023-04-12

SQL injection in Custom 404 Pro (3.7.0 and older)

Affected: 3.7.0 and older
Fixed in: 3.7.1
Access needed (per CVSS): Needs an admin-level account
Range from: CVE record (the advisory publisher) · score by NVD

Details from the advisory

Auth. SQL Injection') vulnerability in Kunal Nagar Custom 404 Pro plugin <= 3.7.0 versions.

NVD CVE-2022-47605 Patchstack advisory

medium 4.3 CVE-2023-0385 · published 2023-01-18

Cross-site request forgery (CSRF) in Custom 404 Pro (3.7.1 and older)

Affected: 3.7.1 and older
Fixed in: 3.7.2 *
Access needed (per CVSS): No login needed; someone on the site has to click a link or open a page
Range from: CVE record (the advisory publisher) · score by NVD

Details from the advisory

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.

NVD CVE-2023-0385 Wordfence advisory Plugin source

medium 6.1 CVE-2019-15838 · published 2019-08-30

Reflected cross-site scripting (XSS) in Custom 404 Pro (older than 3.2.8)

Affected: older than 3.2.8
Fixed in: 3.2.8
Access needed (per CVSS): No login needed; someone on the site has to click a link or open a page
Range from: NVD analysis · score by NVD

Details from the advisory

The custom-404-pro plugin before 3.2.8 for WordPress has reflected XSS, a different vulnerability than CVE-2019-14789.

NVD CVE-2019-15838 wordpress.org wpvulndb.com

medium 6.1 CVE-2019-14789 · published 2019-08-15

Cross-site scripting (XSS) in Custom 404 Pro (3.2.8 only)

Affected: 3.2.8 only
Fixed in: 3.2.9 *
Access needed (per CVSS): No login needed; someone on the site has to click a link or open a page
Range from: NVD analysis · score by NVD

Details from the advisory

The Custom 404 Pro plugin 3.2.8 for WordPress has XSS via the wp-admin/admin.php?page=c4p-main page parameter.

NVD CVE-2019-14789 wordpress.org pluginvulnerabilities.com

Recent activity

2026-08-30 — latest release on wordpress.org (3.16.0).
2025-12-22 — Cross-site request forgery (CSRF) disclosed (CVE-2025-62880), fixed in 3.12.1.
2025-10-11 — SQL injection disclosed (CVE-2025-9947), fixed in 3.12.1.
2024-08-01 — Cross-site scripting (XSS) disclosed (CVE-2024-39646), fixed in 3.11.2.

Free. We check the CVE feeds every day and email you only when a new issue for Custom 404 Pro (custom-404-pro) is published or a fix ships. Unsubscribe in one click.

Browse vulnerabilities

Types found in this plugin: Cross-site scripting (XSS) (6) · SQL injection (3) · Cross-site request forgery (CSRF) (2)

Where this data comes from

Version, last update, installs: wordpress.org/plugins/custom-404-pro (Plugins API), fetched 2026-11-04.
Vulnerabilities: NIST National Vulnerability Database (NVD), checked 2026-11-04. This product uses data from the NVD API but is not endorsed or certified by the NVD.
Each record links to its CVE page and to the original advisory (Wordfence, Patchstack or WPScan) where there is one. We only list a CVE here when its references or its advisory name this exact plugin, so a few real issues may be missing; none should be about a different plugin. Spot an error? Email Daniel.

Badge for your site or docs (states facts with a date, not a verdict):

<a href="https://laskyr.com/plugins/custom-404-pro"><img src="https://laskyr.com/plugins/custom-404-pro/badge.svg" alt="Custom 404 Pro vulnerability status"></a>

← Check another plugin · Free hacked-site scan

Is Custom 404 Pro safe? Known vulnerabilities and latest version

No known unpatched vulnerabilities in the latest version (3.16.0)

What to do

Check your version

Known vulnerabilities

Cross-site request forgery (CSRF) in Custom 404 Pro (3.12.0 and older)

SQL injection in Custom 404 Pro (3.12.0 and older)

Cross-site scripting (XSS) in Custom 404 Pro (3.11.1 and older)

Stored cross-site scripting (XSS) in Custom 404 Pro (3.10.0 and older)

Reflected cross-site scripting (XSS) in Custom 404 Pro (3.8.1 and older)

SQL injection in Custom 404 Pro (older than 3.8.1)

Reflected cross-site scripting (XSS) in Custom 404 Pro (older than 3.7.3)

SQL injection in Custom 404 Pro (3.7.0 and older)

Cross-site request forgery (CSRF) in Custom 404 Pro (3.7.1 and older)

Reflected cross-site scripting (XSS) in Custom 404 Pro (older than 3.2.8)

Cross-site scripting (XSS) in Custom 404 Pro (3.2.8 only)

Recent activity

Get an email when Custom 404 Pro has a new vulnerability

Browse vulnerabilities

Where this data comes from