Posts Auto Expire Control Security & Risk Analysis

wordpress.org/plugins/post-auto-expire-control

Post Auto Expire Control is for admin of multi-authors site to control the posts expiration based on the user role and post type.

30 active installs v0.1.3 PHP + WP 3.2+ Updated Sep 11, 2013
auto-expirationexpiration-controlpost-expirationpost-typeuser-role
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Posts Auto Expire Control Safe to Use in 2026?

Generally Safe

Score 85/100

Posts Auto Expire Control has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.

No known CVEs Updated 12yr ago
Risk Assessment

The "post-auto-expire-control" plugin v0.1.3 exhibits a mixed security posture. On the positive side, it shows good practices by not utilizing dangerous functions, all SQL queries are prepared, and there are no recorded vulnerabilities. However, significant concerns arise from its attack surface and lack of proper authentication checks on entry points. With 4 out of 5 entry points lacking authentication, this plugin is highly susceptible to unauthorized actions. The presence of a taint flow with unsanitized paths, even without a critical or high severity rating, warrants attention as it suggests potential for unintended data manipulation or execution. The lack of capability checks on AJAX handlers is a particularly critical oversight that, combined with the high number of unprotected entry points, exposes the plugin to considerable risk.

While the absence of a vulnerability history is a positive sign, it should not be interpreted as a guarantee of future security. The current code analysis reveals substantial weaknesses in access control and input sanitization for its AJAX handlers, which are the primary vectors for potential exploitation. The plugin needs immediate attention to implement robust authentication and capability checks on all AJAX endpoints to mitigate the identified risks.

Key Concerns

  • AJAX handlers without auth checks
  • Unprotected entry points (4/5)
  • Flows with unsanitized paths
  • Output escaping only 45% proper
  • Capability checks missing
  • Nonce check only 1
Vulnerabilities
None known

Posts Auto Expire Control Security Vulnerabilities

No known vulnerabilities — this is a good sign.
Version History

Posts Auto Expire Control Release Timeline

v0.1.3Current
v0.1.2
v0.1.1
v0.1
Code Analysis
Analyzed Apr 16, 2026

Posts Auto Expire Control Code Analysis

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

Output Escaping

45% escaped22 total outputs
Data Flows · Security
1 unsanitized

Data Flow Analysis

1 flows1 with unsanitized paths
<add_rule_ajax> (html/add_rule_ajax.php:0)
Source (user input) Sink (dangerous op) Sanitizer Transform Unsanitized Sanitized
Attack Surface
4 unprotected

Posts Auto Expire Control Attack Surface

Entry Points5
Unprotected4

AJAX Handlers 4

noprivwp_ajax_adding_rule_ajaxpost-auto-expire-control.php:41
authwp_ajax_adding_rule_ajaxpost-auto-expire-control.php:42
noprivwp_ajax_updata_meta_ajaxpost-auto-expire-control.php:44
authwp_ajax_updata_meta_ajaxpost-auto-expire-control.php:45

Shortcodes 1

[apext-expire] post-auto-expire-control.php:88
WordPress Hooks 9
actioninitpost-auto-expire-control.php:33
actionadmin_menupost-auto-expire-control.php:34
actionadmin_initpost-auto-expire-control.php:35
actionadd_meta_boxespost-auto-expire-control.php:37
actionsave_postpost-auto-expire-control.php:38
actionadmin_print_styles-post-new.phppost-auto-expire-control.php:39
actionadmin_print_styles-post.phppost-auto-expire-control.php:40
actionpost_expirepost-auto-expire-control.php:46
actioninitpost-auto-expire-control.php:48

Scheduled Events 1

post_expire
Maintenance & Trust

Posts Auto Expire Control Maintenance & Trust

Maintenance Signals

WordPress version tested3.6.1
Last updatedSep 11, 2013
PHP min version
Downloads7K

Community Trust

Rating100/100
Number of ratings1
Active installs30
Developer Profile

Posts Auto Expire Control Developer Profile

TC.K

1 plugin · 30 total installs

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

How We Detect Posts Auto Expire Control

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/post-auto-expire-control/css/apext.css/wp-content/plugins/post-auto-expire-control/css/apextmetabox.css/wp-content/plugins/post-auto-expire-control/js/jscontrol.js
Script Paths
/wp-content/plugins/post-auto-expire-control/js/jscontrol.js

HTML / DOM Fingerprints

CSS Classes
apext-expire-date-field
Data Attributes
data-apext-expire
JS Globals
apext_options
Shortcode Output
[apext-expire]
FAQ

Frequently Asked Questions about Posts Auto Expire Control