plugin
7 known security issues reported for the Leenkme WordPress plugin. Most recent disclosed Oct 29, 2024.
Running Leenkme on your site? Check whether your installed version is affected.
Scan your site free[en] Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') vulnerability in Lew Ayotte leenk.Me allows Reflected XSS.This issue affects leenk.Me: from n/a through 2.16.0.
The leenk.me plugin for WordPress is vulnerable to Reflected Cross-Site Scripting in versions up to, and including, 2.16.0 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick...
[en] The leenkme plugin before 2.6.0 for WordPress has stored XSS via facebook_message, facebook_linkname, facebook_caption, facebook_description, default_image, or _wp_http_referer.
[en] The leenkme plugin before 2.6.0 for WordPress has wp-admin/admin.php?page=leenkme_facebook CSRF.
This WordPress leenk.me plugin is prone to cross-site request forgery and cross-site scripting vulnerabilities via vulnerable page: wp-content/plugins/leenkme/facebook.php. Also, there are vulnerable fields: "facebook_message", "facebook_description", "default_image", "facebook_linkname", etc. Upgrade the plugin.
The leenkme plugin before 2.6.0 for WordPress has stored XSS via facebook_message, facebook_linkname, facebook_caption, facebook_description, default_image, or _wp_http_referer.
The leenkme plugin before 2.6.0 for WordPress has wp-admin/admin.php?page=leenkme_facebook CSRF.
Run a free security scan to detect vulnerable plugins and themes, exposed files, and malware — no plugin install, no signup.
Scan your site free