• v7.71.1 Stable

    tech released this 2026-10-20 13:37:14 +00:00 | 61 commits to main since this release

    • The Bot Protection page is now organised in tabs: Overview, Activity, Bot Signatures, Exceptions &
      Lists, Protection Policies and Automation Observation. Every setting and exception works exactly
      as before, and saving one tab never changes the settings of another.
    • Includes the findings improvements below (7.71.0) and the readable menus and form fields in light
      and dark mode (7.70.4).
    Downloads
  • v7.70.3 Stable

    tech released this 2026-10-20 08:00:45 +00:00 | 62 commits to main since this release

    • Fixed a case where blocking the web server's own address in ARGUS stopped WordPress's scheduled
      tasks, so the site could no longer report to the portal or receive the instruction to unblock
      it. WordPress's own internal scheduler requests are no longer refused by the firewall.
    Downloads
  • v7.70.2 Stable

    tech released this 2026-10-19 20:14:33 +00:00 | 63 commits to main since this release

    • A weak warning that rests on a single piece of evidence, such as two failed logins for "admin",
      is now described clearly (how many attempts, for which username, between which times) and no
      longer asks you to act. If nothing more happens it closes by itself after 7 days, or as soon as
      the address is blocked or trusted. If a second kind of evidence appears it is raised as before.
    • Findings that were already open for this kind of warning are tidied up automatically when the
      plugin updates. Nothing you already handled is changed.
    Downloads
  • v7.70.1 Stable

    tech released this 2026-10-19 20:01:46 +00:00 | 64 commits to main since this release

    • You can now switch "Automation observation" on or off for this site from the ARGUS portal as well as
      from the Bot Protection page. It still only records signs of automated visitors and never blocks,
      challenges or changes anything for your visitors, and a switch set in the site's configuration file
      still takes priority.
    Downloads
  • v7.70.0 Stable

    tech released this 2026-10-19 14:01:48 +00:00 | 65 commits to main since this release

    • New, optional "Automation observation" setting on the Bot Protection page. When you switch it on,
      ARGUS quietly records signs of automated or inconsistent visitors (for example a browser identity
      that does not match its other headers, or bursts of requests) and prepares a daily report. It
      never blocks, challenges or changes anything for your visitors, it is off by default, and you can
      turn it off at any time. Details are kept for 14 days and summaries for 90.
    Downloads
  • v7.69.1 Stable

    tech released this 2026-10-19 13:49:41 +00:00 | 66 commits to main since this release

    • Earlier findings about repeated suspicious requests that were only allowed are now closed
      automatically only after ARGUS has proven, with a quick built-in test, that its automatic
      challenge really works on your site. If the test cannot pass, those findings stay open and ARGUS
      records why and tries again every hour.
    Downloads
  • v7.69.0 Stable

    tech released this 2026-10-19 13:37:36 +00:00 | 67 commits to main since this release

    • Fixed a blank page after using Archive, Resolve, Acknowledge and the other actions on a finding
      once you had switched tabs or pages in Findings. You now return to the same tab and page, and a
      refused action is shown as an error instead of a success message.
    • The same threat arriving from many different addresses is now challenged automatically, instead of
      staying "allowed" however many addresses it came from. The thresholds are unchanged.
    • The "Needs Attention" tab in Findings is now called "Critical & High", which is exactly what it
      shows. Medium and low findings stay under "Active".
    • If ARGUS cannot apply a block or challenge, you now see a single clear finding about it instead of
      nothing, and a challenge that cannot be issued no longer shows a page nobody can complete.
    • Finding descriptions now say how many different sources a threat came from, rather than implying
      every request came from the most recent address.
    • Findings about a threat that was only "allowed" before this fix are closed automatically on update, with their evidence kept, and re-open if the threat comes back unchallenged.
    Downloads
  • v7.68.0 Stable

    tech released this 2026-10-19 08:50:50 +00:00 | 68 commits to main since this release

    • The ARGUS portal now receives your complete list of findings and blocked addresses, not just the
      most recent ones, so the numbers it shows for your site are accurate.
    • A threat first detected while Monitor Mode was on no longer lowers your Protection Score once its
      source address is confirmed to be blocked on your site.
    Downloads
  • v7.67.0 Stable

    tech released this 2026-10-18 12:42:57 +00:00 | 69 commits to main since this release

    • Hardened Sitemap Discovery against a crafted sitemap URL being used to make ARGUS fetch an
      unintended internal or external address. Normal sitemap discovery on your own site is
      unaffected.
    • A finding where ARGUS already quarantined the file (status "Contained") no longer counts
      against your Protection Score once that quarantine is confirmed still in effect -- only a
      cleanup decision (restore or permanently delete) remains, now shown separately as "Mitigated
      -- cleanup decision required" instead of as an active threat.
    Downloads
  • v7.66.0 Stable

    tech released this 2026-10-15 14:06:19 +00:00 | 70 commits to main since this release

    • New: ARGUS can now email you when it finds something serious, instead of only showing it on the
      Findings page. Turn it on and set a minimum severity under Settings > Overview > Email Alerts --
      multiple findings in the same few minutes arrive as one digest email, not one email each.
    • Hardened the optional page cache against two cross-visitor cache-sharing risks: a request with
      an unrecognised Host could previously create its own separate cached copy of a page, and a
      tracking link parameter (utm_*, fbclid, gclid, and similar) could in theory end up baked into a
      cached page shared with other visitors. Both are now blocked before the page is cached. Legitimate
      cache-sharing between visitors on the same clean URL is unaffected.
    Downloads