Remove CPT base

Remove CPT base has one disclosed vulnerability in the WordSec catalog, all reported in 2022; it is fixed as of September 2026. Their average CVSS score is 8.8, and the most serious one scores 8.8 out of 10. Severity breakdown: 0 critical and 1 high.

The most common weakness is Cross-Site Request Forgery (CSRF), behind 1 of the records (100%).

The one issue recorded for Remove CPT base has a vendor fix available, so running the current release closes it.

All of these findings were reported by R3N0. Remove CPT base is installed on roughly 10,000 WordPress sites, so each unpatched flaw has a wide blast radius. The current release is tested up to WordPress 6.9.7.

Strategic Overview

Avg CVSSHigh

8.8/ 10

Patch Coverage100%

Open

Fixed

Get automatic notifications for all Remove CPT base vulnerabilities before they are exploited.

Highest severity on recordCVSS 8.8CVE-2022-29431

Remove CPT base <= 5.8 - Cross-Site Request Forgery to CPT base deletion

Read the full analysis

Vulnerability Records

1 records


2022-05-06 13:29	Remove CPT base <= 5.8 - Cross-Site Request Forgery to CPT base deletion Remove CPT base <= 5.8	`CVE-2022-29431`	8.8 High	R3N0	Yes

Showing 1–1 of 1 reports

Latestv6.7

Remove CPT base

Author

kubiq

5.0(33)

100/100

Last Updated

2025-12-01 (10mo ago)

Active Installs

10,000+

Downloads

102,648

Requires WP

3.0+

Requires PHP

5.6+

Tested up to

WP 6.9.7

Created

2017-11-06 (9y ago)

Remove custom post type base slug from url possibility to select specific custom post type(s) auto redirect old slugs to no-base slugs Yoast SEO specifics If you’re using Yoast SEO plugin, after you change something in the Remove CPT base plugin, you should deactivate Yoast SEO and activate it back again to refresh its yoast_indexable database table, so it will generate correct og:url, canonical url and JSON-LD urls.

View on WordPress.org