SMNTCS Disable REST API User Endpoints Security & Risk Analysis

wordpress.org/plugins/smntcs-disable-rest-api-user-endpoints

Disable the REST API user endpoints due to obscure user slugs.

6K active installs v2.4 PHP 5.6+ WP 5.5+ Updated Dec 31, 2024
endpointsrest-apisecurity
92
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is SMNTCS Disable REST API User Endpoints Safe to Use in 2026?

Generally Safe

Score 92/100

SMNTCS Disable REST API User Endpoints has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.

No known CVEs Updated 1yr ago
Risk Assessment

The "smntcs-disable-rest-api-user-endpoints" plugin, version 2.4, exhibits an exceptionally strong security posture based on the provided static analysis. The absence of any identified attack surface, dangerous functions, direct SQL queries, unescaped output, file operations, external HTTP requests, or nonces is a significant strength. The plugin's code also demonstrates meticulous attention to security by relying entirely on prepared statements for any potential SQL interactions (though none were found). The taint analysis further reinforces this, revealing no potentially unsanitized data flows, indicating robust input handling. The vulnerability history, with zero recorded CVEs across all severities and no recent disclosures, suggests a history of responsible development and maintenance.

However, a notable concern arises from the complete lack of capability checks and nonce checks. While the plugin's stated purpose (disabling REST API user endpoints) might imply it doesn't require direct user interaction or permissioned actions, this absence of standard security mechanisms could be a vulnerability if the plugin's functionality were ever to expand or be misinterpreted. The plugin appears to be designed for a very specific, low-risk function with no direct user interaction, which is commendable. The overall security is excellent for its current, narrowly defined scope.

Key Concerns

  • Missing capability checks
  • Missing nonce checks
Vulnerabilities
None known

SMNTCS Disable REST API User Endpoints Security Vulnerabilities

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

SMNTCS Disable REST API User Endpoints Code Analysis

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

SMNTCS Disable REST API User Endpoints Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 1
filterrest_endpointssmntcs-disable-rest-api-endpoints.php:31
Maintenance & Trust

SMNTCS Disable REST API User Endpoints Maintenance & Trust

Maintenance Signals

WordPress version tested6.7.5
Last updatedDec 31, 2024
PHP min version5.6
Downloads29K

Community Trust

Rating100/100
Number of ratings2
Active installs6K
Developer Profile

SMNTCS Disable REST API User Endpoints Developer Profile

Niels Lange

20 plugins · 20K total installs

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

How We Detect SMNTCS Disable REST API User Endpoints

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/smntcs-disable-rest-api-user-endpoints/smntcs-disable-rest-api-endpoints.php
Version Parameters
smntcs-disable-rest-api-user-endpoints/smntcs-disable-rest-api-endpoints.php?ver=2.4

HTML / DOM Fingerprints

REST Endpoints
/wp/v2/users/wp/v2/users/(?P<id>[\d]+)
FAQ

Frequently Asked Questions about SMNTCS Disable REST API User Endpoints