mi13-access-by-link Security & Risk Analysis

wordpress.org/plugins/mi13-access-by-link

Доступ к Вашим постам (на утверждении) по ссылке для модераторов.

0 active installs v1.3 PHP + WP 6.4.0+ Updated Unknown
access-by-linkpendingprivacy-link
100
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is mi13-access-by-link Safe to Use in 2026?

Generally Safe

Score 100/100

mi13-access-by-link has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.

No known CVEs
Risk Assessment

The mi13-access-by-link plugin v1.3 exhibits a mixed security posture. On the positive side, the absence of any known vulnerabilities in its history, coupled with the use of prepared statements for all SQL queries, suggests good development practices in those areas. The code also shows some attention to security with a capability check implemented. However, the static analysis reveals significant concerns regarding its attack surface. With two AJAX handlers identified, and crucially, both lacking authentication checks, this presents a direct and immediate risk. This means that unauthenticated users can potentially interact with these handlers, opening the door for various attacks depending on their functionality. The lack of nonce checks on these AJAX endpoints further exacerbates this risk. The taint analysis showing zero flows is positive, but this might be influenced by the limited scope or complexity of the plugin's code and doesn't negate the identified attack vectors.

Key Concerns

  • AJAX handlers without authentication checks
  • Missing nonce checks on AJAX endpoints
  • Unescaped output in 33% of outputs
Vulnerabilities
None known

mi13-access-by-link Security Vulnerabilities

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

mi13-access-by-link Code Analysis

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

Output Escaping

67% escaped18 total outputs
Attack Surface
2 unprotected

mi13-access-by-link Attack Surface

Entry Points2
Unprotected2

AJAX Handlers 2

authwp_ajax_mi13_access_by_linkmi13-access-by-link.php:283
noprivwp_ajax_mi13_access_by_linkmi13-access-by-link.php:284
WordPress Hooks 5
actionplugins_loadedmi13-access-by-link.php:21
actionpublish_postmi13-access-by-link.php:78
actionadd_meta_boxesmi13-access-by-link.php:83
actionadmin_menumi13-access-by-link.php:113
actionadmin_initmi13-access-by-link.php:136
Maintenance & Trust

mi13-access-by-link Maintenance & Trust

Maintenance Signals

WordPress version tested6.9.4
Last updatedUnknown
PHP min version
Downloads1K

Community Trust

Rating0/100
Number of ratings0
Active installs0
Developer Profile

mi13-access-by-link Developer Profile

mi13

7 plugins · 20 total installs

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

How We Detect mi13-access-by-link

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/mi13-access-by-link/languages/

HTML / DOM Fingerprints

CSS Classes
content-areasite-mainentry-headerentry-titleentry-contententry-footerpost-thumbnail
Data Attributes
id="primary"id="main"role="main"class="content-area"class="site-main"class="post-thumbnail"+10 more
Shortcode Output
<div id="primary" class="content-area"> <main id="main" class="site-main" role="main"> <article> <div class="post-thumbnail"> $thumbnail </div> <header class="entry-header"> <h1 class="entry-title">$title</h1> </header> <div class="entry-content"> $content </div> <footer class="entry-footer"> $cat </footer> </article> </main> </div>
FAQ

Frequently Asked Questions about mi13-access-by-link