Limited-Time Offer

Get Extra 20% off on FullCharge Yearly Plan — available for first 10 users only. Don’t miss out! 🚀

TrackWP

SilentShield · Version history

SilentShield changelog and version history

Latest version
2.15.16
Oct 8, 2026 (1 month ago)
Releases
128
since 2022
In the last year
44
about one every 8 days
Tested up to
WordPress 7.1.4
PHP 7.4 or later

Releases each year

  • 202217 releases
  • 202323 releases
  • 202419 releases
  • 202534 releases
  • 202635 releases

202635 releases

  1. SilentShield 2.15.16Latest

    • Fix [Formidable Forms]: The captcha now appears above the submit button. Current Formidable versions print the submit button as a form field, so the captcha was added underneath it. It is now placed directly in front of the button.

  2. SilentShield 2.15.15

    • Fix [Protection]: Logging in with a password manager’s autofill no longer fails with the honeypot method. Bitwarden ignores autocomplete="off" and filled the invisible honeypot field together with the login form, so the plugin took the login for a bot and refused it. The field now carries Bitwarden…

  3. SilentShield 2.15.14

    • Fix [Protection]: IP protection no longer turns away people who log in again shortly after. The waiting period between two submissions is meant to slow down form floods, but it also applied to the login form: anyone who logged out and straight back in, or who mistyped a password and tried again, wa…
    • Improvement [Protection]: When the IP protection does refuse a submission, the visitor now reads what to do — “Too many attempts in a short time. Please wait a moment and try again.” — instead of the bare label “IP check”. The text is translated in all 26 languages.
    • Improvement [Admin]: SilentChat is live: the “Coming soon” label on the API page is now a link to silentchat.de.

  4. SilentShield 2.15.13

    • Fix [WooCommerce]: Block checkout: orders are no longer refused when the SilentShield API protection is switched on. The block checkout hands its form data to the plugin separately instead of through the regular form submission, so the API protection never saw the behaviour token the page had produ…
    • Fix [WPForms]: WPForms forms could fail to send a second time right after a submission attempt. The form was stopped before the plugin had decided whether to let it through, so a resubmit within the protection window was swallowed. The check now runs first, and if anything is unclear the form is re…
    • Improvement [Admin]: The API page and the Analytics screen no longer show detection-rate figures (such as 99 %) that could not be backed up. The dashboard now tells apart “active”, “key present but protection off” and “key missing”.
    • Improvement [Admin]: When the API protection is on and the site is served over plain http, an admin notice explains that the protection needs a secure connection (localhost is exempt).

  5. SilentShield 2.15.12

    • Fix [Protection]: Jetpack and WPForms: with gibberish detection set to block, genuine messages are no longer turned away. Both form plugins send an encoded status value along with every form — Jetpack a long security token, WPForms a block of usage data. Gibberish detection read these values as tex…
    • Fix [Protection]: In the WordPress comment form, gibberish detection checks the commenter’s name again. Version 2.15.11 had stopped reading it.
    • Improvement [Compatibility]: Tested with Germanized for WooCommerce 4.1 — classic and block checkout with its order button and terms checkbox, the EU withdrawal form, and account login and registration. Every order placed in these tests is also checked in WooCommerce itself: accepted orders are sto…

  6. SilentShield 2.15.11

    • Fix [Protection]: Gibberish detection now works in Elementor, WPForms and Formidable forms — until now it could never block anything there. These form plugins send their fields as a nested group (Elementor as form_fields[…], WPForms as wpforms[fields][…], Formidable as item_meta[…]), and the detect…
    • Fix [Protection]: Gravity Forms: gibberish detection no longer counts one of the form’s hidden fields against every submission. Gravity Forms sends an encoded status field with each form, and the detection read it as text and scored it as random characters — one “suspicious” field in every submissi…
    • New [Forms]: The Forms screen now shows whether the plugin can read your forms. Next to each integration a badge says whether the fields your visitors fill in are recognised, and selecting the integration shows the details: a self-test with a sample submission in that form plugin’s format, the name…
    • Improvement [Compatibility]: Tested with WordPress 7.1 and PHP 8.5. On PHP 8.5, every image captcha shown to a visitor wrote a deprecation notice to the PHP error log; on sites that log notices, that could fill the log quickly. It no longer does, and neither does the one notice the plugin caused on…

  7. SilentShield 2.15.10

    • Fix [Captcha]: After a typo, the corrected answer now goes through — in Elementor, Jetpack, Ninja Forms, Forminator and Kadence forms. Each captcha can be answered once: the attempt uses it up, whether the answer was right or wrong. These five form plugins send the form in the background and leave…
    • Fix [Captcha]: The captcha no longer stops reloading for visitors who share an address. Loading a new captcha is limited to 30 times per minute per IP address, to keep bots from farming them. That limit was meant to start over every minute but only did so after a full minute without a single reques…
    • Fix [Privacy]: The privacy-policy text on the Privacy page now describes the SilentShield API correctly. It said, in all languages, that data is processed exclusively on servers in Germany by Hetzner, never transferred to third countries, and kept for at most 14 days. The servers are STRATO’s; Clou…

  8. SilentShield 2.15.9

    • Improvement [Captcha]: The hint above the image captcha can now be changed. Templates 1 and 6 show “Enter the characters shown in the image:” above the image instead of the captcha label, and that text was fixed — the label setting had no effect on it, and the only way to change it was a translatio…

  9. SilentShield 2.15.8

    • Fix [SilentShield API]: The page shown next to a blocked submission is now the page your site actually served, not one the sender claimed. That address was taken from the browser’s referrer header, which whoever sends the request is free to set to anything at all, or to leave out entirely. A bot do…
    • Fix [Ultimate Member]: Blocked sign-ins and blocked registrations are counted separately now. Both forms were reported under a single name, so your statistics could not say whether you were looking at attempts to guess passwords for existing accounts or at attempts to create fake ones — two rather…
    • Fix [Ultimate Member]: A refused sign-in was counted three times. Ultimate Member checks the entered credentials itself, and doing so set this plugin’s WordPress-login protection going a second and a third time on the very same submission. One refused sign-in therefore produced three entries in you…

  10. SilentShield 2.15.7

    • Improvement [SilentShield API]: Your dashboard now counts every submission this plugin turns away, not just one kind of it. Until now only a single case was reported — a submission that arrived without the behaviour token, typically a bot running no JavaScript. Everything else the plugin refuses on…
    • Improvement [SilentShield API]: Reports now name the form that was hit, so a dashboard can show which of your forms is under attack instead of only that something was. Forms whose integration cannot name them are still reported, just without the name.
    • Improvement [SilentShield API]: The plugin version now travels with the regular key check, so SilentShield can tell you in your dashboard when a site is running an outdated version. Previously the version was only ever sent with the anonymous daily usage statistics — which carry no key and therefor…

  11. SilentShield 2.15.6

    • Fix [API]: The cause behind 2.15.4’s refused submissions is now closed off for good. That release repaired the five integrations where the SilentShield API rejected every genuine visitor as a bot, but it repaired them one by one — the route that let them go wrong was still open, and any integration…
    • Fix [API]: With the API switched off — which is how it ships — every form still carried a hidden field and a small script belonging to it, for a library that was never loaded on those sites. They did nothing and were sent to every visitor on every page with a form. They are now only added when the…
    • Fix [API]: On a site protected by the API alone, with no other protection switched on, forms carried no SilentShield markup at all. The plugin looked as though it were not installed while the server refused everything the page sent, which is the hardest version of this to diagnose from the outside.…

  12. SilentShield 2.15.5

    • Fix [IP protection]: On any site whose timezone is not UTC, IP protection refused legitimate submissions. After one successful submission, every further submission from the same IP address was refused for the length of the site’s offset from UTC — two hours on a German site in summer time — no matt…
    • Fix [IP protection]: The counter behind “max retries” ignored its time window and counted every attempt still on record rather than only those inside the configured period, which made a block possible on attempts that were hours or days apart. It now honours the window.
    • Improvement [IP protection]: A submission is now let through, and the reason written to the log, whenever the check cannot reach a sound verdict — a stored time that lies in the future or cannot be read, a missing internal key, or a database error. Previously the last of these ended the submission…

  13. SilentShield 2.15.4

    • Fix [Elementor, JetFormBuilder, Avada, Gravity Forms, Ultimate Member]: With the SilentShield API switched on, every genuine submission on these five was refused as a bot. The API decides using a token the plugin puts into the form, and on these five integrations that field was never added — so not…
    • Fix [JetFormBuilder]: Settings made for a single JetFormBuilder form applied only when a submission was checked, not when the form was drawn. A protection switched on for one particular form was therefore expected by the check but never placed in the form — and every submission of that form was ref…

  14. SilentShield 2.15.3

    • Fix [Privacy]: The plugin’s own settings screens loaded a font from Google’s servers. Opening any SilentShield page in the WordPress admin fetched the “Inter” typeface from fonts.googleapis.com, and a request to Google’s servers carries the IP address of whoever made it. On a plugin whose purpose i…

  15. SilentShield 2.15.2

    • Fix [Protection]: On some hosts, every form submission failed with a server error. The gibberish detection used PHP’s mbstring extension, which is optional and which WordPress itself does not require — it supplies replacements for the two functions it needs and no more. Where the extension was miss…
    • Improvement [Protection]: While rewriting the above, six characters turned out to have been counted as consonants: the Turkish ı and İ, the Nordic ø, and long vowels such as ā and ū. Names written with them looked slightly less pronounceable to the detection than they are — a small bias against Tur…
    • Fix [Forminator, Ninja Forms]: When a submission was refused, the explanation was attached to the form’s first field so it would appear next to it — but “first” was taken literally, and a form that begins with a hidden field (a tracking value, a pre-filled ID) had the message attached to something…
    • Fix [Elementor]: The same check on a form built entirely from hidden fields left nowhere to put the message, and it was dropped. It is now shown above the form instead.
    • The full changelog, back to the first release, is in changelog.txt in the plugin folder and online.

  16. SilentShield 2.15.1

  17. SilentShield 2.14.0

  18. SilentShield 2.13.0

  19. SilentShield 2.12.1

  20. SilentShield 2.12.0

  21. SilentShield 2.11.0

  22. SilentShield 2.10.0

  23. SilentShield 2.7.6

  24. SilentShield 2.7.5

  25. SilentShield 2.7.3

  26. SilentShield 2.6.8

  27. SilentShield 2.6.7

  28. SilentShield 2.6.6

  29. SilentShield 2.6.5

  30. SilentShield 2.3.5

  31. SilentShield 2.3.4

  32. SilentShield 2.3.3

  33. SilentShield 2.3.2

  34. SilentShield 2.3.1

  35. SilentShield 2.3.0

202534 releases

  1. SilentShield 2.2.61

  2. SilentShield 2.2.60

  3. SilentShield 2.2.581

  4. SilentShield 2.2.59

  5. SilentShield 2.2.58

  6. SilentShield 2.2.57

  7. SilentShield 2.2.56

  8. SilentShield 2.2.55

  9. SilentShield 2.2.54

  10. SilentShield 2.2.53

  11. SilentShield 2.2.52

  12. SilentShield 2.2.51

  13. SilentShield 2.2.50

  14. SilentShield 2.2.49

  15. SilentShield 2.2.48

  16. SilentShield 2.2.47

  17. SilentShield 2.2.46

  18. SilentShield 2.2.45

  19. SilentShield 2.2.44

  20. SilentShield 2.2.43

  21. SilentShield 2.2.42

  22. SilentShield 2.2.41

  23. SilentShield 2.2.4

  24. SilentShield 2.2.3

  25. SilentShield 2.2.2

  26. SilentShield 2.2.1

  27. SilentShield 2.2.0

  28. SilentShield 2.1.2

  29. SilentShield 2.1.1

  30. SilentShield 2.1.0

  31. SilentShield 2.0.702

  32. SilentShield 2.0.701

  33. SilentShield 2.0.700

  34. SilentShield 2.0.7

202419 releases

  1. SilentShield 2.0.682

  2. SilentShield 2.0.681

  3. SilentShield 2.0.68

  4. SilentShield 2.0.66

  5. SilentShield 2.0.65

  6. SilentShield 2.0.64

  7. SilentShield 2.0.63

  8. SilentShield 2.0.62

  9. SilentShield 2.0.61

  10. SilentShield 2.0.6

  11. SilentShield 2.0.5

  12. SilentShield 2.0.4

  13. SilentShield 2.0.3

  14. SilentShield 2.0.2

  15. SilentShield 2.0.1

  16. SilentShield 2.0.0

  17. SilentShield 1.12.1

  18. SilentShield 1.12.0

  19. SilentShield 1.11.92

202323 releases

  1. SilentShield 1.11.8

  2. SilentShield 1.11.7

  3. SilentShield 1.11.6

  4. SilentShield 1.11.5

  5. SilentShield 1.11.4

  6. SilentShield 1.11.3

  7. SilentShield 1.11.2

  8. SilentShield 1.11.0

  9. SilentShield 1.10.0

  10. SilentShield 1.9.1

  11. SilentShield 1.9

  12. SilentShield 1.8

  13. SilentShield 1.7.2.1

  14. SilentShield 1.7.2

  15. SilentShield 1.7.1

  16. SilentShield 1.6.6

  17. SilentShield 1.6.5

  18. SilentShield 1.6.4

  19. SilentShield 1.6.3

  20. SilentShield 1.6.2

  21. SilentShield 1.6.1

  22. SilentShield 1.6

  23. SilentShield 1.5.3

202217 releases

  1. SilentShield 1.5.1

  2. SilentShield 1.5

  3. SilentShield 1.4.93

  4. SilentShield 1.4.92

  5. SilentShield 1.4.91

  6. SilentShield 1.4.9

  7. SilentShield 1.4.8

  8. SilentShield 1.4.7

  9. SilentShield 1.4.6

  10. SilentShield 1.4.5

  11. SilentShield 1.4.4

  12. SilentShield 1.4.3

  13. SilentShield 1.4.2

  14. SilentShield 1.4.1

  15. SilentShield 1.2.2

  16. SilentShield 1.2.1

  17. SilentShield 1.2

Questions about SilentShield’s releases

What is the latest version of SilentShield?

2.15.16, released on Oct 8, 2026 (1 month ago). It’s tested up to WordPress 7.1.4 and needs PHP 7.4 or later.

How often is SilentShield updated?

44 releases in the last year, about one every 8 days. Its first release on WordPress.org dates from January 2022.

Know when your rivals ship

Track your plugin and its rivals: TrackWP sees each new release in the nightly snapshot and alerts you, with what it did to their rank.

Start free

Release dates come from the day each version’s folder was made in SilentShield’s WordPress.org SVN repository; the notes from its readme’s changelog, as its authors wrote it.