Deskripzioa
shieldwave.io by ensomedia.dev
Ensomedia Security, powered by shieldwave.io, scans your site from the inside and tells you, in plain language, what is wrong and how to fix it. It is built around one idea: an alert has to be worth your attention. Every check, the scheduled scans and the email alerts are free, work without an account and have no limits.
Why owners switch to it
- Official checksums first. WordPress core, directory plugins and directory themes are compared with the exact files WordPress.org published for your version. A file that matches is trusted and never “looks suspicious”; a file that differs is reported with the reason.
- Malware detection that needs real evidence. One weak signal, such as base64 in a file, is never a finding. The scanner looks for code that runs what a visitor sends, executes hidden payloads, hides function names, fetches remote code or creates hidden administrators. Findings it is not sure about go under “Ask your developer to check” and never send email.
- Change monitoring for what WordPress.org cannot verify. Premium plugins, custom themes, must-use plugins and drop-ins are recorded as a baseline. Changes that come with an update are accepted; a new PHP file that appears without one is reported.
- Alerts that do not cry wolf. One email per scan, only for problems that are new or got worse, never twice for the same one, at most four a day. A check that could not run never sends an email and never marks anything as fixed.
- Login protection and two-factor login. Password guessers are locked out for a while, user names stay private, and an optional one-time code from an authenticator app makes a stolen password not enough.
- Light on your server. Scans never run while a visitor’s page loads: they run in the background in short steps that fit hosts with a 30-second limit, and files that did not change are not analyzed again.
- Never rewrites your site on its own. The plugin never edits, moves or deletes your files, users or settings by itself. It explains each fix. It acts only when you press a button: it deletes an unused plugin you tick and confirm, the same as Delete on the Plugins screen. Apart from that it refuses only a bad login and a stranger asking for your user list, and it does what you switch on yourself: file editor and XML-RPC off.
The checks
- Malware and backdoors in every PHP, JavaScript and .htaccess file that WordPress.org cannot vouch for: web shells, request-to-execute code, decode-and-execute chains, obfuscated function names, remote code loaders, PHP hidden in images, spam mailers, hidden administrators, injected JavaScript and malicious redirects.
- Core, plugin and theme files against the WordPress.org checksums or release packages of your versions, plus PHP files those releases do not contain.
- File changes outside those releases against the recorded baseline, and plugin or theme folders that appear without going through the WordPress installer.
- PHP files in uploads, and .htaccess or .user.ini rules that make the server run uploads as PHP.
- Known vulnerabilities (opt-in) in plugins, themes and WordPress, premium ones included, with the version that fixes each one. Free and without an account; see External services.
- Closed, abandoned and unused plugins and themes, WordPress, plugin and theme updates and PHP version support.
- Injected content: scripts, hidden iframes and spam links in posts, widgets and options. Ordinary embeds and tracking codes are left alone.
- Exposed files that your web server hands out to anyone (copies of wp-config.php, database dumps, backups, .git folders, .env files, logs), confirmed by requesting them from your own site; leftover installers and database tools; folder listings.
- Accounts and configuration: administrators, user registration, wp-config.php, debug output, file editor, XML-RPC, HTTPS, user list exposure and suspicious scheduled tasks.
Each issue has a severity, what it means, how to fix it and the files, plugins or settings involved. Problems of the same kind are grouped, so a site never faces hundreds of lines. You can ignore a problem; an ignored file comes back if it changes again.
Live protection (three features, all opt-in, off until you turn them on):
- Known vulnerabilities: the lookup described above.
- Live threat feed: new malware rules and file signatures from ShieldWave reach your site within about an hour, verified by signature. It sends nothing about your site.
- AI second opinion: for a file the local rules cannot judge, a redacted excerpt gets a verdict in plain words. Configuration, credential, backup and log files are never sent. See External services.
All three run from WP-Cron once an hour, whether or not a scan is running; the AI second opinion also runs after a scan.
Login protection and two-factor login
- After five failed logins from one address (you choose), that address waits a cooldown you set. The lock is always temporary, and trusted addresses, including the one that turned the feature on, are never locked.
- Failed logins are also counted per user name, across all addresses: 20 an hour by default, any number from 1 to 500, and 0 turns the limit off. Password reset requests are limited per address in the same way: 5 an hour by default, 0 turns it off.
- Only the connection’s own address counts, never a header a request can fake. If the site sits behind a proxy or CDN, list its addresses or CIDR ranges (a range of /8 or narrower, up to 20 entries) under trusted proxies and choose the header that carries the visitor’s address; that header is read only for requests that come from a listed proxy.
- An email goes out when the user name of an administrator gets locked. It is on by default and has its own switch.
- User names stay private: the login form, the ?author=N trick, the REST API user list, embeds and the users sitemap stop giving them to visitors who are not logged in.
- Login protection is on by default for new installs and off after an upgrade until you turn it on. Every lockout goes to History and can raise an alert.
Two-factor login
- Two-factor login is turned on for the site with one switch. Each administrator then sets up an authenticator app for their own account under ShieldWave > Settings. The code is asked for on every login form. Ten recovery codes and
wp shieldwave two-factor disable <user>make sure nobody is locked out. Apps sign in with an application password.
Hardening
- Turn off the plugin and theme file editor and XML-RPC with one switch each, without editing wp-config.php or any other file. ShieldWave warns you first if a plugin you use, such as Jetpack, needs XML-RPC.
Both are off until you turn them on.
Activity log
History is kept in its own database table. Ordinary entries form a chain: each carries a hash, keyed with a secret from wp-config.php, that includes the hash of the entry before it, and the plugin keeps a separate record of the newest one. Check history integrity in History then tells whether an entry was edited or deleted outside ShieldWave, including entries cut off the end. Login lockouts and limited password reset requests are counted in place, one entry per address per hour, and stay outside the chain, so a flood of them cannot break it; their deletion is not detected. Entries are kept for the number of days you set (7 to 730, 90 by default), and the log can be exported as CSV.
Privacy
When logins are paused after too many failed attempts, the plugin records the IP address and the typed user name (the name only when the account exists) for the retention period above, so that password guessing can be blocked. After a successful login it sets a cookie whose name starts with shieldwave_kd_. It holds only a random identifier, lets that browser keep signing in while someone else guesses the password for the same account, expires after 90 days and stops working when the password changes. The plugin adds a suggested text to Settings > Privacy and takes part in the WordPress personal data export and erasure tools for these records. The two-factor secrets of an account are sign-in credentials, not visit records, and the erasure tool leaves them alone.
Alerts
Email after scheduled scans for new or more serious issues at or above your threshold, in real time when an account becomes administrator (naming who did it and, on a network, on which site) and when the user name of an administrator gets locked, and a weekly summary if you want one.
ShieldWave dashboard (optional)
Press Connect with shieldwave.io under ShieldWave > Settings, sign in or create a free account, and the site shows up in your dashboard at shieldwave.io with its score and open issues, next to ShieldWave’s outside scan. A free account shows one site; Pro and Enterprise show every site. The connection sends results only and confirms that the domain is yours; the dashboard cannot change anything on the site. See External services.
What this plugin does not do
It is not a full web application firewall and it does not clean malware out of files for you. It finds, explains, alerts, stops brute-force logins, adds two-factor login, and can switch off the file editor and XML-RPC; you, your developer or your host make the rest of the change. Visitors see nothing of it.
Who builds it
shieldwave.io by ensomedia.dev. Ensomedia Security is designed, built and maintained by ENSOMEDIA, the web and software practice of Radosław Fedorczuk in Wrocław, Poland, which also runs the shieldwave.io outside scanner and dashboard this plugin can connect to.
Credits
The admin screens use the Inter typeface by The Inter Project Authors, licensed under the SIL Open Font License 1.1 (assets/fonts/inter-license.txt). It is loaded from the plugin itself, only on the ShieldWave screens.
External services
The plugin makes no outside requests when it is activated or when admin pages load. Requests happen when a scan runs (by hand or on the schedule), when you use the account actions, and, from WP-Cron once an hour, for the live protection features you turned on and for the check-in of a connected account. Requests to WordPress.org and to your own site use the WordPress HTTP API’s default user agent, which includes your WordPress version and site address, exactly as WordPress itself does for its update checks. Requests to ShieldWave send a neutral user agent (ShieldWave-Security and the plugin version) and never your site address in their headers. Like any web request, each one comes from your server’s IP address.
WordPress.org core checksums (api.wordpress.org/core/checksums/1.0/)
Used by the “WordPress core files” check. Sent: your WordPress version and package language. Cached for a day.
WordPress.org release list (api.wordpress.org/core/stable-check/1.0/)
Used by the “WordPress core files” check to know which older releases to compare with. Sent: nothing about your site; it is a plain request for the public list. Cached for a day.
WordPress.org plugin checksums (downloads.wordpress.org/plugin-checksums/)
Used by the “Plugin files” check. Sent: the folder name and version of each installed plugin, one request per plugin. Cached for a week, or for a day when no list was available.
WordPress.org theme packages (downloads.wordpress.org/theme/)
Used by the “Theme files” check. The release package of each installed directory theme is downloaded to a temporary file, hashed and deleted at once. Sent: the theme’s folder name and version. The result is cached for a week.
WordPress.org plugin information (api.wordpress.org/plugins/info/1.2/)
Used by the “Closed and abandoned plugins” check. Sent: the folder name of each installed plugin. Cached for a day.
All five are provided by WordPress.org: privacy policy.
Your own site
The XML-RPC, debug output and exposed files checks request a few URLs of your own site (xmlrpc.php, the debug.log URL, backup files found on disk, the uploads folder). While a scan runs, the plugin also calls your own admin-ajax.php to continue the scan in the background.
ShieldWave vulnerability lookup (shieldwave.io, endpoint /api/plugin/vulnerabilities), off until you turn it on
Used by the “Known vulnerabilities” check. Sent when that check runs: your WordPress version and the folder name and version of each installed plugin and theme, premium ones included. A premium plugin’s product name is compared on your site, never sent. No site address, no account, no personal data. The answer lists the vulnerabilities that apply to those versions; the data comes from Wordfence Intelligence, and each result links to its record with its copyright notice. The link is shown only for a short list of vulnerability databases (Wordfence, NVD, CVE.org, WPScan, Patchstack, shieldwave.io, WordPress.org and the GitHub advisory database). Runs with the scan and once an hour from WP-Cron; cached for a few hours.
ShieldWave threat feed (shieldwave.io, endpoint /api/plugin/intel), off until you turn it on
Used by the “Live threat feed” option. The plugin downloads a signed file of extra malware rules and known-bad and known-good file signatures, once an hour from WP-Cron, so detection improves between plugin updates. Sent: nothing about your site; the only thing that leaves is your plugin version, which every request already carries. The file is verified with a cryptographic signature before it is used.
ShieldWave AI second opinion (shieldwave.io, endpoint /api/plugin/ai/review), off until you turn it on
Used by the “AI second opinion” option, and only for a file the local rules cannot judge on their own. Sent: an excerpt of up to 6,000 characters around the suspicious code, plus the file’s SHA-256 and MD5 fingerprints and size, the folder name of its plugin or theme, the matched rule identifiers, the site language, the plugin version and a salted hash of the site. Before it is sent, the plugin removes your site address, email addresses, IPv4 and IPv6 addresses, the server path of WordPress and of home folders (replaced by a neutral path), every DB_ constant and the arguments of database connections, constants and values named like a password, key, salt, secret or token (from 6 characters), and long random tokens. Other web addresses stay. For PHP found inside an image, the excerpt starts at the first PHP tag, not at the picture data. Files named wp-config*, .env*, .htpasswd, .user.ini, php.ini or auth.json, backup copies (.bak, .old, .orig, .save, .swp, names ending in ~), database dumps (.sql), logs and .ini files are never read. If the redaction fails, nothing is sent. shieldwave.io passes the excerpt to an AI provider of shieldwave.io, described in the ShieldWave privacy policy; the verdict is kept by the file’s fingerprint and shared across sites. Runs after a scan and once an hour from WP-Cron.
Link to the outside check (shieldwave.io)
After a scan, the Overview shows one line with a link to the free outside check at shieldwave.io. It is an ordinary link: nothing is sent when the page loads. If you click it, your …
Pantaila-argazkiak
Instalazioa
- Install the plugin from Plugins > Add Plugin, or upload the
ensomedia-securityfolder to/wp-content/plugins/. - Activate it.
- Open ShieldWave and press Scan now. The first scan records the baseline and usually takes a few minutes; later scans are faster.
- Scheduled scans run daily at 03:00 (site time). Change that, the alerts and the options under ShieldWave > Settings.
- Optional: turn on the known-vulnerability lookup under ShieldWave > Settings > Live protection.
- Optional: to see the site in the ShieldWave dashboard, press Connect with shieldwave.io under ShieldWave > Settings > ShieldWave account.
MEG
-
Do I need a ShieldWave account?
-
No. All 23 checks, scheduled scans, email alerts and the vulnerability lookup work without one, with no limits.
-
Can I hide ShieldWave from the toolbar?
-
Yes. Under ShieldWave > Settings > Toolbar, turn off “Show ShieldWave in the toolbar”. The choice is per administrator. Visitors never see it.
-
How is this different from other security scanners?
-
It trusts the files WordPress.org can vouch for, needs real evidence before it calls something malware, and emails only about problems that are new or got worse. The goal is that every alert you get is one you would want.
-
What does “Ask your developer to check” mean?
-
The scanner found something unusual that is often harmless: for example a new PHP file in a premium plugin without an update. It is listed so someone who knows the site can look at it, and it never sends an email on its own. Problems under “Fix now” are the ones with clear evidence.
-
A finding is about a file I changed on purpose.
-
Open the item and press “Ignore”. It stays out of the score and the alerts, and an ignored file comes back by itself if it changes again. Ignored items stay under the “Ignored” link below the to-do list, where “Restore” brings one back.
-
Will it slow my site down?
-
No. Scans never run while a visitor’s page loads: they work in the background in steps of a few seconds, and later scans skip files that were clean and did not change. On a busy shared host you can choose the low scan speed in Settings.
-
What happens to the scheduled scan when the clocks change?
-
It stays on the hour you chose, in the time zone set under Settings > General, and it follows a change of that time zone at once. On the one day a year the clocks skip the chosen hour, the scan runs right after the skipped hour. On the day an hour happens twice, it runs once, the first time the clock shows it.
-
Which outside requests does it make?
-
Only when scans run: to WordPress.org for checksums, theme packages, plugin information and the list of WordPress releases, and to your own site. With the vulnerability lookup, live threat feed or AI second opinion on: to shieldwave.io, once an hour from WP-Cron and after scans. With an account connected: to shieldwave.io, also once an hour. Each of those is off until you turn it on, and the External services section below lists exactly what is sent.
-
Why does the plugin register a public AJAX action?
-
The AJAX action
shieldwave_workerlets a running scan continue in the background; it does nothing without the random token of the running scan. The plugin’s REST routes answer administrators only. -
With login protection on, the REST API user list answers only logged-in requests, so an anonymous request for an author gets an error. To keep the list public, add
add_filter( 'shieldwave_hide_user_list', '__return_false' );to a small plugin or to your theme’s functions.php. The same filter also brings back the author fields in embeds and the users sitemap. -
Does it work on multisite?
-
Yes, network-wide. Scanning, the schedule, alerts, the settings screens and the optional ShieldWave account all live on the main site, in the Network Admin, for network administrators only. Every other site of the network enforces the same choice made there: when login protection, two-factor or a hardening switch is on, it is on for that site too, with no separate settings screen to set up. A lockout after failed logins is shared by the whole network, not counted per site, so an address cannot dodge the limit by trying a different site.
-
Does it work without WP-Cron?
-
Yes. If WP-Cron is disabled or loopback requests are blocked, scans still run while the ShieldWave screen is open, and scheduled scans run whenever your server cron calls wp-cron.php.
-
How is the score calculated?
-
It starts at 100. For each check, the most serious open issue takes off points: critical 30, high 15, medium 8, low 3. Ignored issues, hints and checks that could not run take nothing off.
-
Which languages does it speak?
-
English, Arabic, Chinese (Simplified), Dutch, French, German, Indonesian, Italian, Japanese, Korean, Polish, Portuguese (Brazil), Russian, Spanish, Swedish, Turkish and Vietnamese. The screens, the login protection and the alert emails follow the language of your WordPress admin, and Arabic gets a right-to-left layout. Regional variants such as Spanish (Mexico), German (Switzerland) or French (Canada) use the main language. A translation from translate.wordpress.org, once one is complete, takes precedence.
-
The old ShieldWave Security from shieldwave.io is installed too.
-
Builds downloaded from shieldwave.io before the directory listing were called ShieldWave Security, numbered up to 3.6.6, and live in the folder shieldwave-security. They cannot update themselves to this plugin. Keep Ensomedia Security active, deactivate ShieldWave Security, then delete it on the Plugins screen: the settings, results and two-factor set-ups carry over, because Ensomedia Security keeps them while the old copy’s clean-up runs. The Plugins screen shows a notice while an old copy is installed.
-
What happens to my data when I delete the plugin?
-
The plugin removes its settings, results, tables, scheduled tasks, user settings, and two-factor data. If the site is connected to shieldwave.io, it first asks shieldwave.io to remove the site and its results.
-
What does connecting to shieldwave.io do?
-
It shows the site in your shieldwave.io dashboard with its score and open problems, next to the outside scan of shieldwave.io, and confirms that the domain is yours, which the full outside scan needs. A free account shows one site. Everything in the plugin works the same without it.
-
I think a finding is wrong.
-
Open a topic in this plugin’s support forum with the check name and what you see. False positives are treated as bugs.
-
How do I report a security problem in the plugin?
-
Follow https://shieldwave.io/legal/en/vulnerability-disclosure?utm_source=wordpress&utm_medium=plugin&utm_campaign=readme. Please do not post it in the public support forum.
Berrikuspenak
Ez dago berrikuspenik plugin honentzat.
Laguntzaileak eta Garatzaileak
“Ensomedia Security powered by shieldwave.io” software librea da. Ondoko pertsonek egin dizkiote ekarpenak plugin honi.
Laguntzaileak
Ensomedia Security powered by shieldwave.io 3 eskualde-ezarpenetara itzuli da. Eskerrik asko itzultzaileei beraien ekarpenengatik.
Itzul zaitez Ensomedia Security powered by shieldwave.io zure hizkuntzara.
Garapena interesatzen zaizu?
Araka kodea, begiratu SVN biltegia edo harpidetu garapen erregistrora RSS bidez.
Aldaketen loga
1.1.10
- Login protection: a limit per user name, a limit on password reset requests, trusted proxies as a list of addresses or CIDR ranges with a choice of header, and an email when an administrator’s user name is locked.
- The activity log has its own table, its ordinary entries form a hash chain whose newest entry is recorded apart, so edited, deleted and cut-off entries are found, the retention is set in days and the log can be exported as CSV.
- Privacy: a suggested text for Settings > Privacy, and the WordPress personal data export and erasure tools cover the failed login records.
- The AI second opinion redacts more before anything is sent (IP addresses, paths, all DB_ constants, database connection arguments, secrets from 6 characters), never reads configuration, credential, backup, dump, log and ini files, and starts the excerpt of PHP in an image at the PHP tag.
- The banner that offers live protection now says that the AI second opinion sends redacted excerpts to shieldwave.io and its AI provider.
- The API key is stored encrypted when the server allows it.
- Deleting the plugin asks shieldwave.io to remove a connected site, and removes the tables, scheduled task and user settings this version adds.
- A record link in a vulnerability finding is shown only for known vulnerability databases.
- The readme describes what is sent and how often as the code does it: the threat feed and the lookups run every hour from WP-Cron, live protection has three features.
- Malware detection follows request input more precisely and no longer flags legitimate code. On a test site with 35 popular plugins, 5 themes and WordPress core (52,800 files) it flags nothing, and no file takes more than a fraction of a second. Large PHP files are analysed within a time and memory budget.
- File checks: a file that differs from its release only in line endings matches it, a change made by a recorded update is explained, and a real change stays reported until it is reviewed. Links to other sites and odd file names are one finding per place.
- Known vulnerabilities: when a fixed version exists but WordPress does not offer the update (a plugin closed on WordPress.org, a premium plugin, or an update source that has no newer version), the finding says so and gives the steps for that case.
- HTTPS: when the site address starts with http but every http address redirects to https, this is information, not a problem.
- Login and two-factor: turning two-factor off for the whole site needs the password or a code, a changed or reset password forgets the remembered browsers, wp shieldwave unlock lifts a two-factor lock, and ?author= requests in any form no longer reveal a login name.
- Alerts, notices and log entries use calmer, more precise wording.
- Findings that name user accounts reach a connected shieldwave.io account without the names.
- Every text was reviewed again for natural wording in all 16 languages, and 23 unclear English texts were rewritten.
1.1.9
- Unused plugins can be deleted from their finding: tick the ones to remove (all are ticked) and confirm. It works like Delete on the Plugins screen, so each plugin’s own uninstall runs. Only plugins in use nowhere are listed, never ShieldWave itself, and only for users who may delete plugins on a server where WordPress can write the files.
- On a multisite network, a plugin switched on for one site only is no longer reported as unused.
- Files that an older WordPress release left behind after an update are no longer reported as unknown PHP. Each one matches the checksums of the release it comes from; the check’s summary counts them and nothing needs to be done. A PHP file that no release explains is still reported.
- Fewer false alarms on premium plugins: the storage index files All-in-One WP Migration writes itself, the html2canvas library in Elementor Pro, a base64 image saved with wp_upload_bits(), and $GLOBALS read with a fixed key as in BerlinDB (WP Rocket and others) and ACF Pro.
- An empty debug.log is not reported. A debug log the server refuses to hand out is a low note instead of a high finding; only a log that can really be downloaded stays high.
- A site that works over HTTPS but has http:// in Settings > General gets a low note instead of “Login and dashboard are not served over HTTPS”.
- With TranslatePress active, findings no longer show its #!trpst# markers, and texts follow the language of the admin instead of the site.
- A new rule finds the cmd.exec remote-control backdoor family as critical, also outside the uploads folder. Every file is analysed again under the new rules.
- In the network admin the texts say “network” where a single site says “site”.
- More room in the layout: a wider side margin, a calmer header with smaller tabs, a smaller headline and more space between sections. WordPress notices above the plugin are readable in dark mode.
1.1.8
- A scan no longer stops with an error on hosting whose PHP is built without the tokenizer extension (rare; it is on by default almost everywhere). Without it the malware rules match the raw text, as before 1.1.7.
1.1.7
- A finding about files now says where they are: “in the plugin X 2.3.0 (inactive)”, “in the theme Y”, “in WordPress’s own files” or “in the uploads folder”, and the advice fits that place. An inactive plugin is to be deleted, a plugin from WordPress.org reinstalled, a premium one replaced with a fresh copy from its author, a WordPress file reinstalled from Dashboard > Updates. The same goes into the email alert and into “Copy for your developer”.
- Every finding has “Read more”: a fuller explanation for a developer, where the file comes from, the steps with WP-CLI commands and how to check the fix worked, with a button that copies all of it. The plain message above stays as it was.
- An old copy of ShieldWave Security (2.x or 3.x) left in the plugins folder is no longer reported as malware. Its scanner lists the names of known webshells as text to look for, which read like a webshell. Code-pattern rules now count only where the pattern is code, not inside a string or a translated sentence; real backdoors are still found.
- After a scan, the Overview asks once whether to turn on live protection, with a link to what is sent. “Not now” hides it for 30 days. Nothing is turned on without the click.
- Translations shipped with the plugin now win over an older language pack from translate.wordpress.org, which only fills what the plugin lacks. On Polish sites some sentences showed in English and corrected wording never appeared.
- An empty threat feed says that it has nothing beyond the built-in rules yet, instead of showing three zeros.
- Many screen fixes: the layout is centred on wide screens, titles wrap instead of being cut off, form fields and the selected option read clearly in dark mode, notices above the plugin follow its theme, commands and settings fit a phone, the settings section list stays in view and marks the right section, changed settings that are not saved yet are marked and leaving asks first, no glow under buttons, and one-letter words no longer end a Polish line.
- The link to this site on shieldwave.io opens “My sites”.
1.1.6
- On a multisite network the ShieldWave screens are styled again. In the network admin WordPress names the screen differently from a single site, so the plugin did not recognise its own screens there: the stylesheet did not apply (plain lists, tiny text), History and Settings opened as the Overview, and the footer line was missing.
- WordPress itself is no longer reported as vulnerable for two old records that match every version and that WordPress has never fixed (a blind server-side request through pingbacks and activation keys stored in plain text). An up-to-date site was told “WordPress has 2 known vulnerabilities” and to wait for a fix that is not coming. A real vulnerability in WordPress is still reported with the release that fixes it.
- A WordPress release that WordPress.org marks as insecure is reported with the secure release of its branch, even before the vulnerability databases have a record for the fix.
- A vulnerability in WordPress itself with no fixed release no longer offers the Plugins screen.
1.1.5
- The site and shieldwave.io agree on a language. When the site connects, the plugin tells shieldwave.io the site’s language; an account that has not chosen one yet takes it over, so the emails, reports and dashboard of shieldwave.io come in the language the site already uses. The account’s language is shown next to the account under Settings and follows a change made in the dashboard within the hour.
1.1.4
- Known-vulnerability checks and the threat feed now run every hour instead of every three, so a vulnerability disclosed for one of your plugins or themes is reported, and emailed if alerts are on, within the hour. The lookups are cached on shieldwave.io, so the extra runs cost your site almost nothing. An existing schedule is moved to the new rhythm on update.
1.1.3
- A plain image in the uploads folder is no longer reported as an unknown PHP file. With “Images” switched on in Extra checks, every picture was listed as a high finding (a shop with 200 product photos saw all 200), and the email alert went out for them. An image is now reported only when ShieldWave actually finds PHP code inside it, which it still does.
1.1.2
- The screens keep the size of the WordPress admin on large monitors. Since 1.0.3 the whole plugin was enlarged on windows wider than 1920 pixels (a third bigger at 2560); now a wider window gives the lists more room instead of bigger letters. Only a 4K window at 100% scaling gets one small step up.
- The header, the status band, the lists and the footer share one left and right edge, and the light under the current tab sits exactly on the header’s bottom line.
- A tidier header: a slightly lower headline, the theme switch and Scan now in the same rounded shape.
- More bot traffic in the simulation on the planet, most of it aimed at your site, also when the system asks for less motion.
1.1.1
- The automatic scan stays on the hour you chose. It kept its old clock time after the clocks changed or after you picked another time zone under Settings > General, so “At 03:00” could sit beside “Next scan at 02:00”. Every run now plans the next one from your site’s own time. On the one day the clocks skip the chosen hour, the scan runs right after it; when an hour happens twice, it runs once, the first time.
- The update replaces the schedule of 1.1.0 at once, and nothing is scheduled twice.
- The weekly summary follows your site’s clock in the same way.
- The hours in the list under “At” use your site’s time format, the same as “Next scan”, and “today” and “tomorrow” are right on the days the clocks change.
- “See plans” opens the pricing page with the Pro plan selected.
- After a scan, the Overview shows one plain line about the free outside check at shieldwave.io, with your domain filled in. There is nothing to dismiss, and nothing is sent unless you click it.
- Every link from the plugin to shieldwave.io carries the tags utm_source=wordpress, utm_medium=plugin and utm_campaign=(the screen the link is on), which tell shieldwave.io only which link a visit came from.
1.1.0
- Connect with shieldwave.io in one click, from Settings or the Overview: sign in or create a free account there, press “Connect this site” and you are back. Pasting an API key still works, under “Use an API key instead”.
- A free shieldwave.io account shows one site in the dashboard, with its score and open problems.
- While connected, shieldwave.io confirms that the domain is yours from an invisible tag on the home page, so its full outside scan can run on the site.
- Disconnecting removes the site and its results from shieldwave.io, and a copy of the site at another address (a staging copy) shows as a site of its own.
- The dashboard shows the AI second opinion on a file, and problems you ignored as ignored.
- Known vulnerabilities: plugins whose folder name has capital letters are matched again, and one plugin the lookup cannot read no longer stops the check for all the others.
- The old ShieldWave Security from shieldwave.io and this plugin can be installed side by side without losing anything: deactivating or deleting one leaves the settings, results, schedule and two-factor set-ups of the other alone, and a notice says how to remove the old copy.
- Problems about administrator accounts are sent to the dashboard without the account names, and the texts about what is sent say exactly that.
- “Turn all of it on” beside Live protection on the Overview works without JavaScript too.
1.0.3
- A clearer Overview: every group of problems has its own heading above its list, a row shows the name of the problem, and everything else opens with a click.
- The tabs in the header are easier to see, and the Settings tab shows how many protections are still off.
- The look of shieldwave.io: its colours, and its planet beside the status of your site. The planet marks where your site is and shows a simulation of typical bot traffic; a button beside it stops the motion.
- The screens grow with the window on large monitors, and buttons are easier to hit on phones.
- “New” marks a problem only when some problems are new and others are not.
- When a problem has no WordPress screen to open, “Copy for your developer” is the main button.
- No request for a review while something urgent is open.
- “Turn on” beside Known vulnerabilities opens the right part of Settings, and the time of an AI second opinion no longer says “ago” twice.
- In the dark theme the hour of the automatic scan stays readable while its list is open, and switches that are off have a visible edge.
1.0.2
- Emails display correctly in Outlook on Windows: the button keeps its padding, the fonts stay the same in every part of the message, and a long file path wraps instead of widening the message.
- The ShieldWave mark in emails is in the brand colour, so it shows in Outlook’s dark mode too.
1.0.1
- Translated into Arabic, Chinese (Simplified), Dutch, French, German, Indonesian, Italian, Japanese, Korean, Polish, Portuguese (Brazil), Russian, Spanish, Swedish, Turkish and Vietnamese.
- Right-to-left layout for Arabic and other right-to-left admin languages.
- The ShieldWave mark in the plugin’s header and admin menu, the same as on shieldwave.io.
- Alert emails carry the ShieldWave mark (embedded in the email, nothing is loaded from outside), a clearer layout and a right-to-left layout for Arabic.
- After a few scans, the Overview asks once whether you would review the plugin on WordPress.org. “Later” and “Do not ask again” are remembered per administrator.
1.0.0
- First release in the WordPress.org directory.
- Builds downloaded earlier from shieldwave.io were numbered up to 3.6.6. To switch, deactivate and delete that copy, then install this one; the first scan starts the file history again.