Plugins Condition Security & Risk Analysis

wordpress.org/plugins/plugins-condition

Display plugins condition.

1K active installs v1.09 PHP 8.0+ WP 4.7+ Updated Mar 29, 2026
conditionstate
100
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Plugins Condition Safe to Use in 2026?

Generally Safe

Score 100/100

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

No known CVEs Updated 1mo ago
Risk Assessment

The plugin "plugins-condition" v1.09 exhibits a strong security posture based on the provided static analysis and vulnerability history. The absence of any identified attack surface points, dangerous functions, or taint flows with unsanitized paths is highly positive. Furthermore, the fact that all identified SQL queries utilize prepared statements and all output is properly escaped demonstrates good development practices for preventing common web vulnerabilities. The plugin's history also shows no recorded CVEs, indicating a lack of publicly known security flaws.

While the static analysis is comprehensive and reveals no immediate threats, the complete absence of nonce checks and capability checks across all entry points (even though there are none in this version) is a potential concern if the plugin were to evolve and introduce new functionalities with exposed entry points. However, given the current state of zero entry points, this does not translate to an immediate risk. The lack of file operations and external HTTP requests also contributes to a reduced attack surface. Overall, this plugin appears to be very secure in its current version, with no evidence of exploitable vulnerabilities.

Vulnerabilities
None known

Plugins Condition Security Vulnerabilities

No known vulnerabilities — this is a good sign.
Version History

Plugins Condition Release Timeline

v1.09Current
v1.08
v1.07
v1.06
v1.05
v1.04
v1.03
v1.02
v1.01
v1.00
Code Analysis
Analyzed Mar 16, 2026

Plugins Condition Code Analysis

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

SQL Query Safety

50% prepared4 total queries
Attack Surface

Plugins Condition Attack Surface

Entry Points0
Unprotected0
Maintenance & Trust

Plugins Condition Maintenance & Trust

Maintenance Signals

WordPress version tested7.0
Last updatedMar 29, 2026
PHP min version8.0
Downloads12K

Community Trust

Rating90/100
Number of ratings8
Active installs1K
Developer Profile

Plugins Condition Developer Profile

Katsushi Kawamori

54 plugins · 56K total installs

79
trust score
Avg Security Score
100/100
Avg Patch Time
178 days
View full developer profile
Detection Fingerprints

How We Detect Plugins Condition

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

Asset Fingerprints

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

HTML / DOM Fingerprints

CSS Classes
plugins-condition-admin-wrappc-btn-bluepc-btn-graypc-iconpc-color-dangerpc-color-warningpc-color-infopc-color-success
HTML Comments
Plugins Condition Admin UI
Data Attributes
data-condition-iddata-condition-targetdata-condition-keydata-condition-value
JS Globals
pluginscondition_admin_obj
FAQ

Frequently Asked Questions about Plugins Condition