WordPress security is not only about blocking malicious requests.
A modern security plugin also needs to answer several important questions:
Are my plugins or themes affected by known vulnerabilities?
What security events happened on my website?
Are there suspicious scheduled tasks?
Are important security headers configured correctly?
Is my database carrying malicious or unnecessary data?
Can malware scanning run safely on shared hosting?
Can a scanner distinguish legitimate files from actual threats?
With Nexura Security v1.0.11, we focused on these areas.
This release introduces several new security modules while also improving the scanning architecture to reduce CPU usage, false positives, and unnecessary overhead.
What's New in v1.0.11?
- Vulnerability Scanner
The new Vulnerability Scanner detects known CVEs affecting installed WordPress plugins and themes.
Instead of relying only on malware detection, the scanner helps identify software that may already have a publicly known security vulnerability.
This gives administrators another important layer of visibility:
Installed Plugin/Theme
↓
Version Detection
↓
Known Vulnerability Check
↓
CVE Information
↓
Security Risk Assessment
The goal is simple: find vulnerable software before attackers find it.
Nexura Security already provides security auditing capabilities for WordPress plugins and themes, and v1.0.11 expands this area with dedicated vulnerability scanning.
- Security Audit Logs
Security events can be difficult to investigate without historical information.
Version 1.0.11 adds Security Audit Logs for tracking important user actions and security events.
Examples include:
Authentication-related events
Administrative actions
Security configuration changes
Important security events
Other activities that may require investigation
Audit logs can be particularly useful when troubleshooting a compromised website.
Instead of asking:
"What happened?"
you can start investigating:
"What changed, when did it change, and which action triggered it?"
- Security Headers Manager
HTTP security headers are an important part of modern website hardening.
Nexura Security v1.0.11 adds a Security Headers Manager supporting:
HSTS
X-Frame-Options
Content Security Policy (CSP)
X-XSS-Protection
The objective is to make common security hardening controls easier to manage directly from WordPress.
For example:
WordPress
│
├── HSTS
├── X-Frame-Options
├── CSP
└── X-XSS-Protection
│
▼
Additional Browser-Side Protection
Headers should still be configured carefully because an overly restrictive policy can break legitimate website functionality.
- Database Security & Safe Cleanup
WordPress databases can accumulate expired transients, unnecessary data, and potentially suspicious entries over time.
The new DB Security & Safe Cleanup module focuses on helping administrators maintain a cleaner database while looking for potentially malicious transients.
The important word here is safe.
Security cleanup should not blindly delete database records.
A security tool should identify what it believes is unnecessary or suspicious and allow administrators to make informed decisions.
- Cron Job Auditor
WordPress scheduled tasks are useful for legitimate automation.
But they can also become interesting persistence mechanisms after a website compromise.
For example, an attacker could attempt to create a scheduled task that periodically executes unwanted activity.
The new Cron Job Auditor helps identify suspicious or hidden WordPress scheduled tasks.
A simplified security workflow looks like:
WordPress Cron Jobs
↓
Audit Scheduled Tasks
↓
Identify Suspicious Entries
↓
Review
↓
Take Action
This adds another layer of visibility for administrators investigating a potentially compromised website.
- Security Score & Reporting
Security tools can generate a lot of information.
But information is only useful if administrators can understand the overall security posture of their website.
Nexura Security v1.0.11 adds Security Score & Reporting to provide a real-time view of the site's security posture.
Instead of checking every security feature individually, administrators can use the security score as a high-level indicator and then investigate individual findings.
Think of it as:
Security Score
│
├── Vulnerabilities
├── Security Headers
├── Malware Detection
├── Authentication
├── Database Security
└── Configuration
The score is designed to provide visibility, not replace detailed security analysis.
Performance Improvements
Security scanning can be expensive on shared hosting.
A scanner that consumes too much CPU can affect the entire WordPress installation.
That's why v1.0.11 includes several architectural changes.
Freemius SDK Removed
Nexura Security has completely removed the Freemius SDK from the plugin.
The result is a more independent architecture with fewer external components inside the plugin.
The focus is now on keeping the security core lightweight and focused on its primary purpose.
More Targeted Malware Signatures
Another major improvement is the reduction and targeting of cloud threat-intelligence signatures.
Instead of attempting to match an unnecessarily broad collection of patterns, the scanner focuses more heavily on targeted PHP and WordPress malware signatures.
This has two important benefits:
Faster scanning
Fewer false positives
False positives are especially problematic for security plugins.
A scanner that continuously reports legitimate files as malware creates alert fatigue and makes real threats harder to identify.
Better CPU Management for Shared Hosting
Shared hosting environments have limited CPU resources.
Running large malware scans without resource management can create unnecessary load.
Nexura Security v1.0.11 introduces a 1.5-second CPU breathing gap between scan steps.
The scanner also reduces the per-step execution time from 10 seconds to 6 seconds.
The basic idea is:
Scan
↓
Short CPU Breathing Gap
↓
Scan
↓
Short CPU Breathing Gap
↓
Scan
↓
...
This approach is designed to make background scanning more friendly to shared hosting environments.
Fewer Malware False Positives
One of the most important improvements in v1.0.11 is more precise malware detection.
The scanner no longer flags legitimate theme and plugin files simply because they contain Windows binary formats such as:
Armadillo
UPX
PE32
Domain-matching YARA rules have also been improved to reduce false positives.
The goal is not simply to detect more.
The goal is to detect better.
Improved Database and Post Content Scanning
Earlier generic cloud YARA patterns could produce large numbers of false positives when scanning database options and post content.
Version 1.0.11 changes this approach.
The database and post-content scanner now uses more targeted injection detection patterns, including indicators such as:
eval ()
<script>
<iframe>
Rather than relying on broad generic malware patterns for every database value, the scanner focuses on indicators that are more relevant to WordPress database injection scenarios.
This significantly reduces unnecessary findings.
Stability Fix: Missing Plugin Files
WordPress administrators sometimes manually delete plugin files or remove incomplete plugin installations.
Version 1.0.11 fixes a fatal error that could occur when specific plugin files were missing or manually deleted.
Security software should be able to handle imperfect installations gracefully.
A missing file should result in a manageable security finding or scan condition—not a fatal error that takes down the process.
Safer Plugin ZIP Uploads
Another technical improvement involves malware regex patterns.
Hardcoded malware regex patterns were moved into an encoded external file.
One practical benefit is reducing the chance of cPanel ClamAV flagging the Nexura Security plugin ZIP during upload because of embedded malware-like regex patterns.
This is especially useful for hosting environments where uploaded plugin packages are automatically scanned.
Why This Release Matters
Nexura Security v1.0.11 is not just a feature update.
The release focuses on three areas:
Security Visibility
CVE detection, audit logs, cron auditing, security headers, and security reporting give administrators more visibility into their WordPress security posture.
Better Detection
More targeted malware signatures and improved database scanning help reduce false positives.
Better Performance
CPU breathing gaps, shorter scan steps, and the removal of unnecessary SDK dependencies make the scanner better suited to resource-constrained hosting environments.
What's Next?
WordPress security is continuously evolving.
New vulnerabilities appear, attackers change their techniques, and security tools need to adapt.
Our goal with Nexura Security is to build a security platform that remains:
Lightweight
Transparent
Performance-focused
Developer-friendly
Practical for shared hosting
Accessible to WordPress users
Version 1.0.11 is another step toward that goal.
Try Nexura Security
Nexura Security is available for WordPress users who want malware scanning, firewall protection, vulnerability auditing, authentication security, and other WordPress hardening features.
👉 Website: https://nexurasecurity.com/
👉 WordPress.org: https://wordpress.org/plugins/nexura-security/
If you're a WordPress developer, security researcher, or website administrator, we'd love to hear your feedback.
What security feature would you like to see in the next release?
