Changing a post type can move existing content between editing workflows, templates, and publication controls. Post Type Switcher version 4.1.1 has successfully completed the CleanTalk Plugin Security Certification process and received PSC-2026-65714. The review focused on editing permissions, target post type validation, individual and bulk changes, editor integration, and preservation of existing content.

Name ofPost Type Switcher
Version4.1.1
Active installations200,000+
DescriptionAdds a post type selector to the editor and supports bulk conversion between posts, pages, and eligible custom post types.
SecuritySuccessfully tested for:
SQL Injection (SQLi)
Cross-Site Scripting (XSS) – Stored and Reflected
Cross-Site Request Forgery (CSRF)
Authentication Vulnerabilities
Authentication Bypass Exploits
Privilege Escalation
Buffer Overflow
Denial-of-Service (DoS) vectors
Data Leakage Vulnerabilities
Insecure Dependency Usage
Remote Code Execution (RCE) Risks
Unauthorized File Access
Insufficient Injection Protection
Information Disclosure via Misconfigured Endpoints
CleanTalk CertificationAwarded PSC-2026-65714 through the CleanTalk Plugin Security Certification program for version 4.1.1.
Additional InformationBack up content before a large conversion and review destination templates, taxonomies, and publication permissions. Choose only post types that fit the intended editorial workflow.
Plugin Security Certification by CleanTalkCleanTalk Plugin Security Certification
Logo of the pluginPost Type Switcher logo

Make security review part of your plugin development process and give WordPress site owners a clear certification reference.

PSC by Cleantalk

Key Features

Post Type Switcher adds a selector to the editing interface so an existing entry can be reassigned to another supported post type. It works with posts, pages, and eligible custom types, and offers bulk editing for groups of entries. The plugin supports the Block Editor as well as Classic Editor workflows. Hidden types are excluded by default, and attachment switching is not part of the documented support.

Security Assurance

The review focused on whether a user can edit the selected content and use the intended destination type. It covered individual changes, bulk requests, editor controls, and the validation of submitted identifiers. The certification also considered output associated with the selector and the handling of existing content during supported conversions.

The plugin has been successfully tested for:

✅ Information Leakage Vulnerabilities

✅ SQL Injection Vulnerabilities

✅ Cross-Site Scripting (XSS) Attacks

✅ Cross-Site Request Forgery (CSRF) Attacks

✅ Authentication and Authentication Bypass Vulnerabilities

✅ Privilege Escalation Vulnerabilities

✅ Buffer Overflow Vulnerabilities

✅ Denial-of-Service (DoS) Vulnerabilities

✅ Data Leakage Vulnerabilities

✅ Insecure Dependencies

✅ Code Execution Vulnerabilities

✅ File Unauthorized Access Vulnerabilities

✅ Insufficient Injection Protection

Conclusion

Post Type Switcher version 4.1.1 is certified under PSC-2026-65714. The reviewed paths cover the controls that change an entry type from the editor or through bulk editing. Keep the plugin updated and check presentation and access rules after conversions, particularly when moving content into a custom post type.

Note: The date and certification information may change over time. It is advisable to verify the latest details on the plugin developer’s website.

Plugin Security Certification (PSC-2026-65714): “Post Type Switcher” – Version 4.1.1

Dmitrii I

Pentester with 5 years of hands-on experience securing WordPress and web applications, holding OSWE, OSEP, OSCP, and OSWP certifications. Author of 450 published CVEs, including 35 disclosed within the last month. Specializes in discovering and validating high-impact vulnerabilities in WordPress plugins/themes / Custom WEB applications and delivering actionable remediation guidance to harden production sites.

Visit Author's Website

See all posts by dmitrii-ignatyev

Leave a Reply

Your email address will not be published. Required fields are marked *