Compare commits
| Author | SHA1 | Date | |
|---|---|---|---|
|
|
8fa6153099 | ||
|
|
c8f8640e4c | ||
|
|
50336dfd90 | ||
|
|
85997bca02 | ||
|
|
3aa96c7b3e | ||
|
|
a8108f9b84 | ||
|
|
d89b0d09a9 | ||
|
|
fa1beeb71d | ||
|
|
68cc299d16 | ||
|
|
5657d78e13 | ||
|
|
0fb24b0e7b | ||
|
|
19957d44b0 | ||
|
|
4054510acc | ||
|
|
a0885f319a | ||
|
|
a8cdbef65a | ||
|
|
806094d6a0 | ||
|
|
0faf78287a | ||
|
|
235169e8ac | ||
|
|
67323f0204 | ||
|
|
f3a00c618b | ||
|
|
d39aa6f9bc | ||
|
|
efb0dfc838 | ||
|
|
7fa580d4d6 | ||
|
|
bd3275d252 |
+6
-6
@@ -1,11 +1,11 @@
|
||||
{
|
||||
"version": "7.42.0",
|
||||
"released_at": "2026-09-17T12:12:41+00:00",
|
||||
"package_url": "https://git-cloud.weboria.eu/Weboria/argus-wp-defence/releases/download/v7.42.0/argus-wordpress-defence-7.42.0.zip",
|
||||
"sha256": "c7821aa239c9a50576e5b3fdf48547ec1e6f0817d656253d4bb85f46fd30dee7",
|
||||
"version": "7.66.0",
|
||||
"released_at": "2026-10-15T14:06:21+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",
|
||||
"sha256": "a1d6796fbce70f75852b76d0a1f95c6ea535240cfae4de728d30ee042826344c",
|
||||
"min_php": "7.4",
|
||||
"min_wp": "6.0",
|
||||
"critical": false,
|
||||
"summary": "* If this site is connected to a WAD account, findings shown there now include ARGUS's full\n explanation -- what was found, why it matters, and what to check -- not just the recommended\n fix, so you no longer need to open wp-admin to see the complete picture.",
|
||||
"signature": "mUeeUqBfwGLpPNBmxtOFy1sLueaBn6Tj/61DYBcOAKoxVvdfIlFQUDSxHyTPgZDGiiy8NVhHJ370znBNkW3EBA=="
|
||||
"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.",
|
||||
"signature": "4B4ZbdfBB7RcFMCt+YEWNJQfhspsGxsm9/RIv8p2O40b23Z+o/mwtGShV02wX66PsYUZlVfPoXnYbexMjHOGCw=="
|
||||
}
|
||||
|
||||
Reference in New Issue
Block a user