WP-CMS Security & Risk Analysis

wordpress.org/plugins/wp-cms

WP-CMS is a plugin for Wordpress that changes the functionality of the Wordpress admin backend to act more like a CMS.

20 active installs v2.1 PHP + WP 2.7+ Updated Aug 17, 2009
adminblogcmscontentpages
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is WP-CMS Safe to Use in 2026?

Generally Safe

Score 85/100

WP-CMS has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.

No known CVEs Updated 16yr ago
Risk Assessment

The "wp-cms" v2.1 plugin exhibits a concerning lack of security best practices, despite its seemingly small attack surface and zero recorded CVEs. The static analysis reveals significant vulnerabilities in how the plugin handles data. All 6 SQL queries are unparameterized, posing a high risk of SQL injection. Furthermore, none of the 3 output operations are properly escaped, creating a strong possibility of cross-site scripting (XSS) vulnerabilities. The taint analysis also flagged 2 flows with unsanitized paths, which, while not classified as critical or high severity in this report, directly correlate with the observed lack of escaping and could lead to serious security breaches if exploited.

The absence of any identified CVEs or past vulnerabilities might suggest a recent or less targeted plugin. However, the internal code quality issues are a significant red flag. The complete lack of capability checks, nonce checks, and proper output escaping on all analyzed entry points (even if the attack surface is currently zero) means that any future expansion or modification of the plugin could introduce critical vulnerabilities. The plugin's current state does not demonstrate robust security architecture, and the identified flaws require immediate attention to prevent potential compromise.

Key Concerns

  • All SQL queries use prepared statements
  • No output operations are properly escaped
  • Taint flows with unsanitized paths found
  • No capability checks
  • No nonce checks
Vulnerabilities
None known

WP-CMS Security Vulnerabilities

No known vulnerabilities — this is a good sign.
Code Analysis
Analyzed Mar 16, 2026

WP-CMS Code Analysis

Dangerous Functions
0
Raw SQL Queries
6
0 prepared
Unescaped Output
3
0 escaped
Nonce Checks
0
Capability Checks
0
File Operations
0
External Requests
0
Bundled Libraries
0

SQL Query Safety

0% prepared6 total queries

Output Escaping

0% escaped3 total outputs
Data Flows
2 unsanitized

Data Flow Analysis

2 flows2 with unsanitized paths
wp_cms_settings (wp-cms.php:53)
Source (user input) Sink (dangerous op) Sanitizer Transform Unsanitized Sanitized
Attack Surface

WP-CMS Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 3
actionadmin_menuwp-cms.php:43
actionadmin_headwp-cms.php:44
actionadmin_headwp-cms.php:45
Maintenance & Trust

WP-CMS Maintenance & Trust

Maintenance Signals

WordPress version tested2.8.4
Last updatedAug 17, 2009
PHP min version
Downloads19K

Community Trust

Rating0/100
Number of ratings0
Active installs20
Developer Profile

WP-CMS Developer Profile

Gilbert Pellegrom

6 plugins · 260 total installs

84
trust score
Avg Security Score
85/100
Avg Patch Time
30 days
View full developer profile
Detection Fingerprints

How We Detect WP-CMS

Patterns used to identify this plugin on WordPress sites during automated security audits and web crawling.

Asset Fingerprints

Asset Paths
/wp-content/plugins/wp-cms/wp-cms.css/wp-content/plugins/wp-cms/wp-cms.js
Script Paths
/wp-content/plugins/wp-cms/wp-cms.js
Version Parameters
wp-cms/wp-cms.css?ver=wp-cms/wp-cms.js?ver=

HTML / DOM Fingerprints

CSS Classes
wp-cms-settings
JS Globals
window.location
FAQ

Frequently Asked Questions about WP-CMS