WP Paging Ajax Security & Risk Analysis

wordpress.org/plugins/wp-paging-ajax

A simple plugin using ajax to paging.

20 active installs v1.0.1 PHP + WP 4.0+ Updated Apr 18, 2017
ajax-paginationajax-pagingpaging
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is WP Paging Ajax Safe to Use in 2026?

Generally Safe

Score 85/100

WP Paging Ajax 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 wp-paging-ajax plugin v1.0.1 exhibits a strong security posture based on the provided static analysis. The absence of AJAX handlers, REST API routes, shortcodes, and cron events significantly limits the plugin's attack surface. Furthermore, the code demonstrates good practices by exclusively using prepared statements for SQL queries and not performing file operations or external HTTP requests. The lack of any known vulnerabilities or recorded CVEs further contributes to its positive security profile.

However, a critical concern arises from the output escaping. With 2 total outputs and 0% properly escaped, there is a high risk of Cross-Site Scripting (XSS) vulnerabilities. Any dynamic data displayed by the plugin, even if processed securely otherwise, could be exploited if not properly escaped. Additionally, the absence of nonce checks and capability checks, while not directly leading to immediate vulnerabilities due to the limited attack surface, represents a missed opportunity for hardening and could become a significant risk if new entry points are introduced in future versions without these security measures.

In conclusion, while the plugin is currently very secure due to its minimal attack surface and lack of known vulnerabilities, the complete lack of output escaping presents a significant and immediate risk. Addressing this output escaping issue should be the top priority to ensure the plugin's continued security.

Key Concerns

  • Unescaped output identified
  • Missing nonce checks
  • Missing capability checks
Vulnerabilities
None known

WP Paging Ajax Security Vulnerabilities

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

WP Paging Ajax Code Analysis

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

Output Escaping

0% escaped2 total outputs
Attack Surface

WP Paging Ajax Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 3
actionadmin_menuincludes\settings.php:13
actionadmin_initincludes\settings.php:14
actionwp_enqueue_scriptswp-paging-ajax.php:34
Maintenance & Trust

WP Paging Ajax Maintenance & Trust

Maintenance Signals

WordPress version tested4.7.32
Last updatedApr 18, 2017
PHP min version
Downloads2K

Community Trust

Rating100/100
Number of ratings1
Active installs20
Developer Profile

WP Paging Ajax Developer Profile

thinhbg59

4 plugins · 10K total installs

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

How We Detect WP Paging Ajax

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/wp-paging-ajax/assets/css/wppa.css/wp-content/plugins/wp-paging-ajax/assets/js/pjax-standalone.js/wp-content/plugins/wp-paging-ajax/assets/js/wppa.js
Script Paths
/wp-content/plugins/wp-paging-ajax/assets/js/pjax-standalone.js/wp-content/plugins/wp-paging-ajax/assets/js/wppa.js
Version Parameters
wp-paging-ajax/assets/css/wppa.css?ver=wp-paging-ajax/assets/js/pjax-standalone.js?ver=wp-paging-ajax/assets/js/wppa.js?ver=

HTML / DOM Fingerprints

JS Globals
WPPA
FAQ

Frequently Asked Questions about WP Paging Ajax