NextCellent Simple History Security & Risk Analysis

wordpress.org/plugins/ngg-simple-history

Add Simple History integration for NextCellent.

70 active installs v2.0.1 PHP + WP 4.0.0+ Updated Apr 1, 2016
activityadminchangelogchangesfeedhistory
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is NextCellent Simple History Safe to Use in 2026?

Generally Safe

Score 85/100

NextCellent Simple History has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.

No known CVEs Updated 10yr ago
Risk Assessment

The 'ngg-simple-history' v2.0.1 plugin exhibits a remarkably clean security posture based on the provided static analysis. The absence of any identified AJAX handlers, REST API routes, shortcodes, or cron events significantly limits its attack surface. Furthermore, the code analysis reveals a complete lack of dangerous functions, no raw SQL queries (all are prepared), and all output is properly escaped. There are also no file operations or external HTTP requests. This indicates a strong adherence to secure coding practices within this version of the plugin. The vulnerability history is also completely clean, with no recorded CVEs, which further bolsters confidence in its security. However, the near-zero attack surface is also notable because it suggests the plugin may have very limited functionality or relies entirely on other plugins to provide its core features. While the code itself appears robust and secure, the lack of any detectable entry points warrants a consideration of its practical impact and potential for future expansion that might introduce vulnerabilities if not managed carefully.

Vulnerabilities
None known

NextCellent Simple History Security Vulnerabilities

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

NextCellent Simple History Code Analysis

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

NextCellent Simple History Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 16
filtersimple_history/loggers_filesclass-ncg-simple-history.php:27
actionadmin_initloggers\NextCellentLogger.php:79
actionngg_created_new_galleryloggers\NextCellentLogger.php:83
actionngg_after_new_images_addedloggers\NextCellentLogger.php:84
actionngg_add_albumloggers\NextCellentLogger.php:85
actionngg_update_album_sortorderloggers\NextCellentLogger.php:86
actionngg_delete_albumloggers\NextCellentLogger.php:87
actionngg_update_albumloggers\NextCellentLogger.php:88
actionngg_update_options_pageloggers\NextCellentLogger.php:89
actionngg_delete_galleryloggers\NextCellentLogger.php:90
actionngg_delete_pictureloggers\NextCellentLogger.php:91
actionngg_update_galleryloggers\NextCellentLogger.php:92
actionngg_gallery_addnewpageloggers\NextCellentLogger.php:93
actionngg_image_updatedloggers\NextCellentLogger.php:94
actionngg_gallery_sortloggers\NextCellentLogger.php:95
actionplugins_loadedngg-simple-history.php:60
Maintenance & Trust

NextCellent Simple History Maintenance & Trust

Maintenance Signals

WordPress version tested4.5.33
Last updatedApr 1, 2016
PHP min version
Downloads2K

Community Trust

Rating0/100
Number of ratings0
Active installs70
Developer Profile

NextCellent Simple History Developer Profile

niknetniko

2 plugins · 120 total installs

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

How We Detect NextCellent Simple History

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

Asset Fingerprints

HTML / DOM Fingerprints

FAQ

Frequently Asked Questions about NextCellent Simple History