
Scheduled stickiness Security & Risk Analysis
wordpress.org/plugins/scheduled-stickinessThis plugin makes a post sticky and unsticky on dates you specify in advance.
Is Scheduled stickiness Safe to Use in 2026?
Generally Safe
Score 92/100Scheduled stickiness has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.
The plugin 'scheduled-stickiness' v0.2 exhibits a generally strong security posture based on the provided static analysis. It demonstrates good practices by avoiding dangerous functions, using prepared statements for all SQL queries, and not performing file operations or external HTTP requests. The absence of any recorded vulnerabilities, including critical or high severity ones, further indicates a robust development approach. However, there are areas for improvement. Notably, only 50% of the total output is properly escaped, presenting a potential for cross-site scripting (XSS) vulnerabilities if the unescaped outputs involve user-supplied data. Additionally, the lack of capability checks on any entry points is a concern, as it means any authenticated user, regardless of their role, could potentially interact with the plugin's functionality, which might not be intended.
Key Concerns
- 50% of output not properly escaped
- No capability checks on entry points
Scheduled stickiness Security Vulnerabilities
Scheduled stickiness Release Timeline
Scheduled stickiness Code Analysis
Output Escaping
Scheduled stickiness Attack Surface
WordPress Hooks 3
Scheduled Events 1
Maintenance & Trust
Scheduled stickiness Maintenance & Trust
Maintenance Signals
Community Trust
Scheduled stickiness Alternatives
No alternatives data available yet.
Scheduled stickiness Developer Profile
1 plugin · 10 total installs
How We Detect Scheduled stickiness
Patterns used to identify this plugin on WordPress sites during automated security audits and web crawling.
Asset Fingerprints
HTML / DOM Fingerprints
<!-- security --><!-- Plugin activated --><!-- Plugin deactivated --><!-- cron -->+8 morename="mknu_sticky_date"id="mknu_sticky_date"name="mknu_unsticky_date"id="mknu_unsticky_date"name="mknu_nonce"