Post Likerator Security & Risk Analysis

wordpress.org/plugins/post-likerator

Simple like/unlike function for posts. No dislikes. Bring your own CSS.

10 active installs v1.0.0 PHP + WP 4.8.2+ Updated Unknown
developer-friendlylikelike-poststhumbs-up
100
A · Safe
CVEs total0
Unpatched0
Last CVENever
Download
Safety Verdict

Is Post Likerator Safe to Use in 2026?

Generally Safe

Score 100/100

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

No known CVEs
Risk Assessment

The "post-likerator" v1.0.0 plugin exhibits a concerning security posture primarily due to its unprotected AJAX endpoints and unsanitized output. While the plugin demonstrates good practice by using prepared statements for all SQL queries and avoiding dangerous functions, its attack surface is small but entirely exposed. The presence of unprotected AJAX handlers is a significant vulnerability that could allow unauthorized actions if exploited. Furthermore, the taint analysis revealing a flow with unsanitized paths, classified as high severity, directly points to a potential for code injection or other execution-based attacks. The lack of any recorded vulnerability history, while seemingly positive, could also indicate a lack of rigorous security auditing or a recently discovered plugin. Overall, the plugin has a few critical weaknesses that outweigh its strengths, necessitating immediate attention to secure the AJAX endpoints and address the unsanitized output.

Key Concerns

  • Unprotected AJAX handlers
  • Taint flow with unsanitized path (high severity)
  • Output escaping not used
  • No capability checks on entry points
Vulnerabilities
None known

Post Likerator Security Vulnerabilities

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

Post Likerator Code Analysis

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

SQL Query Safety

100% prepared8 total queries

Output Escaping

0% escaped7 total outputs
Data Flows
1 unsanitized

Data Flow Analysis

2 flows1 with unsanitized paths
<class.post-likerator> (library\class.post-likerator.php:0)
Source (user input) Sink (dangerous op) Sanitizer Transform Unsanitized Sanitized
Attack Surface
2 unprotected

Post Likerator Attack Surface

Entry Points2
Unprotected2

AJAX Handlers 2

authwp_ajax_post_likerator_ajaxlibrary\class.post-likerator.php:17
noprivwp_ajax_post_likerator_ajaxlibrary\class.post-likerator.php:18
WordPress Hooks 5
actionalllibrary\class.flip_hooks.php:129
actionalllibrary\class.flip_hooks.php:137
actionshutdownlibrary\class.flip_hooks.php:138
actionwp_enqueue_scriptslibrary\class.post-likerator.php:14
actionwp_footerlibrary\class.post-likerator.php:19
Maintenance & Trust

Post Likerator Maintenance & Trust

Maintenance Signals

WordPress version tested4.8.28
Last updatedUnknown
PHP min version
Downloads1K

Community Trust

Rating0/100
Number of ratings0
Active installs10
Developer Profile

Post Likerator Developer Profile

Flipeleven

1 plugin · 10 total installs

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

How We Detect Post Likerator

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/post-likerator/javascript/post-likerator.js
Script Paths
javascript/post-likerator.js
Version Parameters
post-likerator/javascript/post-likerator.js?ver=1.0.0

HTML / DOM Fingerprints

CSS Classes
post-likerator-buttonuser-has-likedpost-likerator-iconpost-likerator-count
Data Attributes
data-post-id
JS Globals
post_likeratorpost_likerator_nonce
REST Endpoints
/wp-json/post_likerator/v1/likes
Shortcode Output
<button class="post-likerator-button<span class="post-likerator-icon"></span><span class="post-likerator-count">
FAQ

Frequently Asked Questions about Post Likerator