Compare commits

..
3 Commits
Author SHA1 Message Date
tech 2ce45b9c2d Update signed manifest to 7.69.0 2026-10-19 13:37:39 +00:00
tech 21ed592b8b Update signed manifest to 7.68.0 2026-10-19 08:50:53 +00:00
tech cc56098488 Update signed manifest to 7.67.0 2026-10-18 12:43:00 +00:00
+7 -7
View File
@@ -1,11 +1,11 @@
{ {
"version": "7.66.0", "version": "7.69.0",
"released_at": "2026-10-15T14:06:21+00:00", "released_at": "2026-10-19T13:37:38+00:00",
"package_url": "https://git-cloud.weboria.eu/Weboria/argus-wp-defence/releases/download/v7.66.0/argus-wordpress-defence-7.66.0.zip", "package_url": "https://git-cloud.weboria.eu/Weboria/argus-wp-defence/releases/download/v7.69.0/argus-wordpress-defence-7.69.0.zip",
"sha256": "a1d6796fbce70f75852b76d0a1f95c6ea535240cfae4de728d30ee042826344c", "sha256": "d1c006de4e32d83d929285c6768633a4c1f21067560bb9a2c24280021e0d9014",
"min_php": "7.4", "min_php": "7.4",
"min_wp": "6.0", "min_wp": "6.0",
"critical": false, "critical": true,
"summary": "* New: ARGUS can now email you when it finds something serious, instead of only showing it on the\n Findings page. Turn it on and set a minimum severity under Settings > Overview > Email Alerts --\n multiple findings in the same few minutes arrive as one digest email, not one email each.\n* Hardened the optional page cache against two cross-visitor cache-sharing risks: a request with\n an unrecognised Host could previously create its own separate cached copy of a page, and a\n tracking link parameter (utm_*, fbclid, gclid, and similar) could in theory end up baked into a\n cached page shared with other visitors. Both are now blocked before the page is cached. Legitimate\n cache-sharing between visitors on the same clean URL is unaffected.", "summary": "* Fixed a blank page after using Archive, Resolve, Acknowledge and the other actions on a finding\n once you had switched tabs or pages in Findings. You now return to the same tab and page, and a\n refused action is shown as an error instead of a success message.\n* The same threat arriving from many different addresses is now challenged automatically, instead of\n staying \"allowed\" however many addresses it came from. The thresholds are unchanged.\n* The \"Needs Attention\" tab in Findings is now called \"Critical & High\", which is exactly what it\n shows. Medium and low findings stay under \"Active\".\n* If ARGUS cannot apply a block or challenge, you now see a single clear finding about it instead of\n nothing, and a challenge that cannot be issued no longer shows a page nobody can complete.\n* Finding descriptions now say how many different sources a threat came from, rather than implying\n every request came from the most recent address.\n* 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.",
"signature": "4B4ZbdfBB7RcFMCt+YEWNJQfhspsGxsm9/RIv8p2O40b23Z+o/mwtGShV02wX66PsYUZlVfPoXnYbexMjHOGCw==" "signature": "T78BKVQ08ouM8bqvKryZ3AN8SxAY+sySZfdBeCJA6jlsJMZO7GrHsnyRnyQ/lh2AcEUXiz9AiHr/syIIe5CDDw=="
} }