Config Constants Security & Risk Analysis

wordpress.org/plugins/config-constants

Modify WP_DEBUG and other WordPress constants directly in the WordPress admin rather than manually editing them via wp-config.php!

100 active installs v0.2 PHP + WP 4.0+ Updated Mar 20, 2017
configconstantdebugmodewp-config-wp-config-php
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Config Constants Safe to Use in 2026?

Generally Safe

Score 85/100

Config Constants has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.

No known CVEs Updated 9yr ago
Risk Assessment

The 'config-constants' plugin v0.2 presents a mixed security picture. On the positive side, the plugin demonstrates good practices by utilizing prepared statements for all SQL queries and has no recorded vulnerabilities or CVEs. The attack surface is also remarkably small, with no identified AJAX handlers, REST API routes, shortcodes, or cron events, indicating a limited potential for direct exploitation. However, a significant concern arises from the complete lack of output escaping, meaning that all 8 identified output points are susceptible to cross-site scripting (XSS) vulnerabilities if they handle user-provided or untrusted data. Additionally, the absence of capability checks and nonce checks on its entry points is a notable weakness, as it doesn't properly verify user permissions or prevent cross-site request forgery (CSRF) for any potential future functionalities.

Key Concerns

  • All output points are unescaped
  • No capability checks implemented
  • No nonce checks implemented
Vulnerabilities
None known

Config Constants Security Vulnerabilities

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

Config Constants Code Analysis

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

Output Escaping

0% escaped8 total outputs
Attack Surface

Config Constants Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 3
actionadmin_initconfig-constants.php:71
actionadmin_menuconfig-constants.php:72
filterplugin_action_linksconfig-constants.php:73
Maintenance & Trust

Config Constants Maintenance & Trust

Maintenance Signals

WordPress version tested4.8.28
Last updatedMar 20, 2017
PHP min version
Downloads7K

Community Trust

Rating100/100
Number of ratings1
Active installs100
Developer Profile

Config Constants Developer Profile

David Gwyer

11 plugins · 109K total installs

69
trust score
Avg Security Score
86/100
Avg Patch Time
156 days
View full developer profile
Detection Fingerprints

How We Detect Config Constants

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/config-constants/
Version Parameters
config-constants/config-constants.php

HTML / DOM Fingerprints

CSS Classes
pcdmdashicons-yesdashicons-no
HTML Comments
/* @todo - Move all CSS to separate file and enqueue only on Plugin options page. - add to class layout rather than functions - only show the info icons on hover - need to disable the functions to write to config file if it's not writable. - Add some more constants from here: https://codex.wordpress.org/Editing_wp-config.php - Could replace globals with class properties once we refactor plugin - Add dismissable notice on plugins page that doesn't show again when dismissed. */
Data Attributes
pcdm_options
FAQ

Frequently Asked Questions about Config Constants