Plugins are now verified against WordPress.org's official per-file checksums, including files added to a plugin that are not part of the official release. Also flags plugins removed from the directory or abandoned, and makes trust revocable so future detection improvements apply retroactively.<\/p>","0.7.34":"
Closes a critical hole: anything able to write into the uploads folder could forge a component backup and have it extracted over a plugin directory on the next Restore. Backups, baselines and scan checkpoints are now signed. Recommended for all sites.<\/p>","0.7.32":"
Fixes four ways this plugin could itself lose data or take a site down (a core-file restore leaving the file missing, a rollback overwriting the destination, a backup restore running with the site live, and a stranded .maintenance file after uninstall), stops one large file stalling the scanner, and restores quarantine recovery on sites upgraded from 0.7.26-0.7.30. Adds a Trusted components screen. Recommended for all sites.<\/p>","0.7.31":"
Follow-up fixes to 0.7.30: restores legacy-quarantine recovery after a reinstall, stops the scanner from restarting without ever finishing, and hardens the 0.7.30 alert and cron-example fixes. Recommended for all sites.<\/p>","0.7.30":"
Fourteen security and correctness fixes from a full review of 0.7.29, several affecting multisite recovery, quarantine rollback, and automatic backups. Recommended for all sites.<\/p>","0.7.29":"
Stops WordPress 6.7+ logging a "translation loaded too early" notice on every admin page load. Recommended if your debug log is filling up.<\/p>","0.7.28":"
Removes a debug warning added in 0.7.25 that flooded the log on sites with WP_DEBUG enabled. No behaviour change otherwise.<\/p>","0.7.27":"
Stops WordPress 6.7+ filling the debug log with a "translation loaded too early" notice on every request. No behaviour change otherwise; 0.7.26's security fix is included.<\/p>","0.7.26":"
Security release. Fixes an arbitrary file write inside the WordPress root: a forged quarantine session could make Rollback overwrite wp-config.php. Affects 0.7.24 and 0.7.25. Update, then review the Remediation screen before clicking Rollback if the site may have been compromised.<\/p>"},"ratings":[],"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3675151,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3675151,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3675151,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3675151,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["0.7.31","0.7.32","0.7.34","0.7.35"],"block_files":[],"assets_screenshots":{"screenshot-1.png":{"filename":"screenshot-1.png","revision":3675151,"resolution":"1","location":"assets","locale":"","width":1616,"height":779}},"screenshots":{"1":"SMEPlan Security Shield Dashboard and Security Scanner Overview."}},"plugin_section":[],"plugin_tags":[8646,1174,31093,163531,600],"plugin_category":[54],"plugin_contributors":[278558],"plugin_business_model":[],"class_list":["post-345738","plugin","type-plugin","status-publish","hentry","plugin_tags-backdoor","plugin_tags-firewall","plugin_tags-hardening","plugin_tags-malware-scan","plugin_tags-security","plugin_category-security-and-spam-protection","plugin_contributors-solotop","plugin_committers-solotop"],"banners":{"banner":"https:\/\/ps.w.org\/smeplan-security-shield\/assets\/banner-772x250.png?rev=3675151","banner_2x":"https:\/\/ps.w.org\/smeplan-security-shield\/assets\/banner-1544x500.png?rev=3675151","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":false,"icon":"https:\/\/ps.w.org\/smeplan-security-shield\/assets\/icon-128x128.png?rev=3675151","icon_2x":"https:\/\/ps.w.org\/smeplan-security-shield\/assets\/icon-256x256.png?rev=3675151","generated":false},"screenshots":[{"src":"https:\/\/ps.w.org\/smeplan-security-shield\/assets\/screenshot-1.png?rev=3675151","caption":"SMEPlan Security Shield Dashboard and Security Scanner Overview."}],"raw_content":"\n
SMEPlan Security Shield is a free, open-source security plugin built around a practical WordPress operations checklist: it watches the 3 most common attack surfaces (OWASP-class attacks plus WordPress-specific ones, persistence mechanisms, and entry vectors), detects issues with baseline\/checksum + signature + thresholded heuristics, and remediates safely (quarantine instead of outright deletion; 1-click rollback).<\/p>\n\n
mu-plugins<\/code>, drop-ins, the active theme\/plugins, and uploads<\/code>; never loads the whole file tree into RAM at once.<\/li>\n- Safe database scanning<\/strong>: keyset pagination (no
OFFSET<\/code>) over options<\/code>\/posts<\/code>\/postmeta<\/code>; only flags a row when it decodes into an actually executable PHP\/JS token, skipping image data URIs.<\/li>\n- Configuration checks<\/strong>:
.htaccess<\/code>\/.user.ini<\/code> rules that map media extensions to PHP, auto_prepend_file<\/code>, file\/directory permissions, weak salts\/keys, unusual cron entries.<\/li>\n- Baseline\/integrity<\/strong>: compares core files against WordPress.org's official checksums; automatically builds a SHA-256 baseline for every plugin\/theme on install\/update; 1-click restore of any mismatched core file from a signature-verified WordPress.org package, with the current file quarantined first.<\/li>\n
- Quarantine & rollback<\/strong>: moves suspicious files aside (never deletes), with a full transaction log and 1-click rollback.<\/li>\n
- Per-component backups<\/strong>: a \"last confirmed good\" snapshot of each plugin\/theme, refreshed on every trusted update, checksum-verified before every restore, with a best-effort local tamper-resistance layer.<\/li>\n
- Maintenance mode with a TTL<\/strong> that turns on automatically when remediation touches a hot path or a large batch, and turns itself off once a health-check passes.<\/li>\n
- Hardening<\/strong>: login rate-limit\/lockout by IP + IP\/username (real IP behind a CDN via trusted proxies), disables XML-RPC pingback + caps
system.multicall<\/code>, security headers (HSTS\/X-Frame-Options\/CSP Report-Only), controlled auto-updates (low-traffic time window, skips VCS-managed sites, health-check after updating).<\/li>\n- Multi-layer scan scheduling<\/strong>: WP-Cron + an internal watchdog + an HMAC-signed REST endpoint (for system cron\/remote pings) + a WP-CLI command \u2014 the schedule keeps running even when WP-Cron is unreliable.<\/li>\n
- Multisite<\/strong>: enumerates every site by
blog_id<\/code>, scanning each site's own uploads<\/code> folder and tables.<\/li>\n<\/ul>\n\nTwo hardening behaviours worth knowing about before you enable them, because they change how the site answers requests that are not this plugin's own:<\/p>\n\n
\n- User-enumeration blocking is on by default.<\/strong> For visitors who are not signed in, the core
wp\/v2\/users<\/code> REST routes stop being served and ?author=<id><\/code> links redirect to the home page. This is a deliberate part of the login-hardening layer, but it is a change to an API this plugin does not own \u2014 a headless front end, a mobile app or a third-party integration that reads the public user list will see it disappear. Turn it off under Hardening if something depends on it. (rc-47)<\/li>\nwp smeplan-ss scan run<\/code> exits 75 when a scan is already running.<\/strong> 75 is EX_TEMPFAIL<\/code> \u2014 \"temporary failure, try again\" \u2014 rather than 0, so a wrapper running under set -e<\/code> will treat a busy lock as a failed command. Handle 75 explicitly if you schedule the command that way. (rc-49)<\/li>\n<\/ul>\n\nNot yet in this release (planned for later versions)<\/h4>\n\n\n- 2FA (TOTP) and CAPTCHA for the login page.<\/li>\n
- Anonymous telemetry (opt-in).<\/li>\n
- Translations (every string is already wrapped in
__()<\/code>, ready for translators via translate.wordpress.org \u2014 no translation is bundled with the plugin itself).<\/li>\n- Action Scheduler integration for enterprise-grade durable queuing.<\/li>\n<\/ul>\n\n
Privacy Policy<\/h3>\n\n
By default, this plugin does not send any data outside of the site it is installed on. Everything it collects (scan findings, logs, baseline data) stays in the local WordPress database and in a protected local storage folder inside the uploads directory (wp-content\/uploads\/smeplan-security-shield\/<\/code>, blocked from direct web access).<\/p>\n\nTwo features send data off-site, and both are entirely opt-in \u2014 off unless the site admin explicitly sets them up:<\/p>\n\n
\n- Alert email<\/strong>: if enabled, a summary of new findings is emailed to the site's configured admin email address (
admin_email<\/code>) using WordPress's own wp_mail()<\/code>.<\/li>\n- Alert webhook<\/strong>: if the admin enters a Webhook URL in Policies, a summary (site URL, alert subject, malicious\/suspicious counts, timestamp \u2014 no personal or visitor data) is sent as JSON to that admin-provided URL whenever new findings are detected. Nothing is sent anywhere unless the admin fills in this field themselves.<\/li>\n<\/ul>\n\n
That storage folder outlives the plugin on purpose: deleting the plugin removes its options, cron events and capabilities, but leaves the folder in place so a quarantined file is never destroyed by an uninstall performed mid-incident. See the FAQ entry \"What is removed when I delete the plugin?\" for the reasoning and for how to remove it yourself.<\/p>\n\n
The plugin does not phone home to any SMEPlan-operated server, does not track usage\/analytics, and does not include any third-party tracking or advertising code.<\/p>\n\n\n
\n- Upload the plugin to
wp-content\/plugins\/<\/code> or install it through the Plugins screen.<\/li>\n- Activate the plugin.<\/li>\n
- Go to Security Shield \u2192 Wizard<\/strong> to check WP-Cron\/loopback and configure trusted proxies if the site sits behind a CDN.<\/li>\n
- See Security Shield \u2192 Policies<\/strong> to turn hardening features on\/off as needed.<\/li>\n<\/ol>\n\n\n
\nDoes the plugin delete suspicious files automatically?<\/h3><\/dt>\nNo. Files at the \"malicious\" level are moved into quarantine<\/strong> (wp-content\/uploads\/smeplan-security-shield\/quarantine\/<\/code>) rather than deleted, and can be rolled back with 1 click. Files at the \"suspicious\" level are only recorded, waiting for manual review on the Findings page.<\/p>\n\nQuarantined files are kept for a limited time: once a session is older than the retention period set under Policies (14 days by default), it is removed automatically to stop the quarantine folder growing without bound. Roll back anything you want to keep before that window closes, or raise the retention setting.<\/p><\/dd>\n
What is removed when I delete the plugin?<\/h3><\/dt>\nDeleting the plugin removes every option it created, its scheduled events, and the three custom capabilities it grants. It deliberately does not remove its storage folder<\/strong> at wp-content\/uploads\/smeplan-security-shield\/<\/code>, which holds the quarantine, the file baseline, the event log and any component backups.<\/p>\n\nThis is a deliberate choice, not an oversight. Quarantined files are moved<\/em>, not copied \u2014 the folder holds the only remaining copy of anything the plugin took out of the site. Deleting a plugin is easy to do in the middle of handling an incident, or by someone who is not the person investigating, and having that click silently destroy both the only rollback path and the only forensic evidence would be the wrong default for a security plugin. Reinstalling brings the previous quarantine and logs straight back.<\/p>\n\nTo remove it, delete that folder yourself over SFTP or your host's file manager once you are sure nothing in it is still needed. Read the caution first:<\/strong> the quarantine\/<\/code> subfolder can contain live malicious files that were pulled off the site. Delete them, do not move them back into place.<\/p><\/dd>\nDoes the plugin automatically edit database content or the .htaccess file?<\/h3><\/dt>\nNo. Every finding in the database or in configuration files (.htaccess\/.user.ini) is only reported, never auto-fixed, to avoid breaking a site's legitimate functionality.<\/p><\/dd>\n
Does this plugin change how WordPress updates itself?<\/h3><\/dt>\nNo. It never supplies its own update source: there is no bundled update checker, no third-party update server, no filtering of the plugin-information API, and nothing written to the transients core caches available updates in. Everything WordPress installs still comes from WordPress.org, fetched and verified by WordPress itself.<\/p>\n\n
What it does offer \u2014 off by default, and only if you switch it on in Policies<\/strong> \u2014 is control over when<\/em> an update WordPress has already found and verified gets applied. Using core's own public auto_update_core<\/code> \/ auto_update_plugin<\/code> \/ auto_update_theme<\/code> filters, it can hold an update back until the low-traffic window you configure, skip it while the site is under load, and skip any plugin or theme directory that is under version control (updating those breaks a deploy). It only ever delays WordPress's own updates; it never substitutes them.<\/p>\n\nSince 0.7.32 it can also refuse one: a plugin or theme package is scanned while still in its temporary folder, and if a file in it matches malware detection the install is stopped before anything is written. A manual update can be allowed through once from the dashboard notice; an automatic one is refused and reported. This uses core's own upgrader_source_selection<\/code> filter, changes nothing about where updates come from, and can be switched off in Policies.<\/p>\n\nAutomated scanners flag any use of those filters for a human to look at, which is why this is spelled out here.<\/p><\/dd>\n
What environment does it need?<\/h3><\/dt>\nWordPress 6.1+, PHP 7.4+. Works best when WP-Cron runs normally; if the site has DISABLE_WP_CRON<\/code> set or blocks loopback requests, use system cron\/WP-CLI following the instructions on the Wizard page.<\/p><\/dd>\n\n<\/dl>\n\n\nNewest release only \u2014 WordPress.org truncates this section at 5,000\ncharacters. The full history is in changelog.txt<\/code>, shipped with the plugin.<\/p>\n\n0.7.35<\/h4>\n\n
Plugins and themes stop being taken purely on trust.<\/p>\n\n
\n- Plugins are now checked against WordPress.org's official per-file checksums.<\/strong> Until this release every integrity check compared the site against ITSELF: a baseline records what a component looked like the first time it was seen, which catches later tampering and says nothing at all about a plugin that was already backdoored before it was seen. WordPress.org publishes a per-file md5 and sha256 for every plugin in the directory, and that answers a question no local history can \u2014 are these the bytes the author shipped? Files that were changed are reported, and so are files that are not part of the official release at all<\/strong>, which is how most backdoors actually arrive: they add a file rather than edit one. (rc-80)<\/li>\n
- Two separate columns, because they answer different questions.<\/strong> \"Matches published files\" is about provenance. \"Upstream\" is about whether that release is still looked after \u2014 including the case that matters most, a plugin removed from the directory<\/strong>, which is often removal because of<\/em> a security problem. A plugin can be perfectly authentic and abandoned three years ago; one combined badge would hide exactly that pairing. Premium and custom plugins have no upstream to compare against and now say so plainly instead of showing a neutral tick. (rc-80)<\/li>\n
- Trust is no longer permanent.<\/strong> Every baseline, every accepted file and every backup now records WHICH generation of the detection rules vouched for it. A payload the rules of the day scored below the threshold gets written into a baseline as the known-good state, and from then on it is<\/em> the definition of correct for that file \u2014 re-running the same rules forever changes nothing. When the rules improve, everything carrying an older stamp is examined again with the detector as it is now, so improvements reach backwards instead of only applying to files first seen afterwards. (rc-79)<\/li>\n
- An accepted file is still a human decision.<\/strong> A rules bump re-scores acceptances, but only a malicious<\/em> verdict overrides the person who accepted it; anything milder leaves the decision standing. Dumping previously triaged findings back on the admin twice is how a Findings screen stops being read. (rc-79)<\/li>\n
- A backup taken under older rules is re-checked before it is restored.<\/strong> Backups are scanned before being zipped, but with the detector of the day \u2014 so an archive can hold a payload those rules did not recognise, and \"Restore from backup\" would put it straight back. Such an archive is now unpacked to a temporary directory and run through the current rules first, and refused with the offending path named if it fails. (rc-79)<\/li>\n
- Baselines record the component's own version.<\/strong> Every automatic caller used to stamp them with the scanner's version instead, so a baseline for WooCommerce 8.4 said \"0.7.32\". That made the field useless for its one purpose and made an upstream lookup impossible, since the checksum file is addressed by the component's own version. (rc-79)<\/li>\n<\/ul>\n\n
Cost: one outbound request per plugin per day, cached hard, on its own cron lane with a queue \u2014 never inside a scan tick, where it would run straight into the per-tick budget.<\/p>\n\n
Older releases: see changelog.txt<\/code>.<\/p>","raw_excerpt":"Scheduled security scanning (files\/DB\/config), baseline\/integrity checks, safe quarantine & rollback, and hardening for WordPress.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/ast.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/345738","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/ast.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/ast.wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/ast.wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=345738"}],"author":[{"embeddable":true,"href":"https:\/\/ast.wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/solotop"}],"wp:attachment":[{"href":"https:\/\/ast.wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=345738"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/ast.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=345738"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/ast.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=345738"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/ast.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=345738"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/ast.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=345738"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/ast.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=345738"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}