Llavero.io Security & Risk Analysis

wordpress.org/plugins/llavero-io

Este plugin permite vincular las cuentas de usuario de WordPress con Llavero.io para tener un segundo factor de authenticación (2FA) en el login de lo …

10 active installs v0.1.4 PHP 5.3+ WP 4.6+ Updated Mar 3, 2018
2faauthenticationloginsecurity
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Llavero.io Safe to Use in 2026?

Generally Safe

Score 85/100

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

No known CVEs Updated 8yr ago
Risk Assessment

The 'llavero-io' plugin exhibits several security concerns despite a clean vulnerability history. The static analysis reveals a significant attack surface with 10 AJAX handlers, of which 8 lack authentication checks. This is a critical vulnerability, as it allows unauthenticated users to interact with potentially sensitive plugin functionalities. Furthermore, all 4 SQL queries are executed without prepared statements, increasing the risk of SQL injection vulnerabilities, especially in conjunction with the unprotected AJAX endpoints. Taint analysis indicates 2 high-severity flows, suggesting potential for data manipulation or unauthorized access, although their exact nature is not detailed here. The absence of nonce checks on AJAX endpoints further exacerbates the risk of Cross-Site Request Forgery (CSRF) attacks. While the plugin has no recorded vulnerabilities, this should not be interpreted as a sign of robust security, given the identified weaknesses in the code itself. The high percentage of properly escaped outputs (84%) and the absence of dangerous functions or file operations are positive signs. However, the numerous unprotected entry points and the reliance on raw SQL queries pose a substantial risk that needs immediate attention.

Key Concerns

  • Unprotected AJAX handlers
  • Raw SQL queries without prepared statements
  • High severity taint flows
  • Missing nonce checks on AJAX
Vulnerabilities
None known

Llavero.io Security Vulnerabilities

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

Llavero.io Code Analysis

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

SQL Query Safety

0% prepared4 total queries

Output Escaping

84% escaped70 total outputs
Data Flows
4 unsanitized

Data Flow Analysis

7 flows4 with unsanitized paths
<config> (includes\views\config.php:0)
Source (user input) Sink (dangerous op) Sanitizer Transform Unsanitized Sanitized
Attack Surface
8 unprotected

Llavero.io Attack Surface

Entry Points10
Unprotected8

AJAX Handlers 10

authwp_ajax_cill_get_user_dataweciberllavero.php:449
authwp_ajax_cill_empezarweciberllavero.php:472
authwp_ajax_cill_desvincular_cuentaweciberllavero.php:519
authwp_ajax_cill_set_apikeyweciberllavero.php:565
authwp_ajax_cill_set_appidweciberllavero.php:596
authwp_ajax_cill_config_testweciberllavero.php:626
authwp_ajax_cill_send_2fanotifyweciberllavero.php:658
noprivwp_ajax_cill_getmeinfoweciberllavero.php:700
noprivwp_ajax_cill_getmeinfo_aperturaweciberllavero.php:784
noprivwp_ajax_cill_send_notificationweciberllavero.php:852
WordPress Hooks 10
actionadmin_menuweciberllavero.php:17
actionadmin_enqueue_scriptsweciberllavero.php:43
actionshow_user_profileweciberllavero.php:174
actionedit_user_profileweciberllavero.php:175
actionpersonal_options_updateweciberllavero.php:231
actionedit_user_profile_updateweciberllavero.php:232
filterwp_authenticate_userweciberllavero.php:241
actionmanage_users_columnsweciberllavero.php:414
actionmanage_users_custom_columnweciberllavero.php:420
actionlogin_enqueue_scriptsweciberllavero.php:696
Maintenance & Trust

Llavero.io Maintenance & Trust

Maintenance Signals

WordPress version tested4.9.29
Last updatedMar 3, 2018
PHP min version5.3
Downloads2K

Community Trust

Rating80/100
Number of ratings4
Active installs10
Developer Profile

Llavero.io Developer Profile

davidnoguera

1 plugin · 10 total installs

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

How We Detect Llavero.io

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/llavero-io/includes/js/cilib.js
Script Paths
https://unpkg.com/node-forge@0.7.0/dist/forge.min.js/wp-content/plugins/llavero-io/includes/js/cilib.js

HTML / DOM Fingerprints

Data Attributes
id="cill_messages"id="cill_appid"id="ciberllaverouserkey"id="ciberllavelogin_user"id="ciberllavelogin_password"name="empezarcill"+4 more
JS Globals
window.cilib
FAQ

Frequently Asked Questions about Llavero.io