Compare commits
| Author | SHA1 | Date | |
|---|---|---|---|
|
|
8fa6153099 | ||
|
|
c8f8640e4c | ||
|
|
50336dfd90 | ||
|
|
85997bca02 | ||
|
|
3aa96c7b3e | ||
|
|
a8108f9b84 | ||
|
|
d89b0d09a9 | ||
|
|
fa1beeb71d |
+6
-6
@@ -1,11 +1,11 @@
|
|||||||
{
|
{
|
||||||
"version": "7.58.0",
|
"version": "7.66.0",
|
||||||
"released_at": "2026-10-07T11:13:22+00:00",
|
"released_at": "2026-10-15T14:06:21+00:00",
|
||||||
"package_url": "https://git-cloud.weboria.eu/Weboria/argus-wp-defence/releases/download/v7.58.0/argus-wordpress-defence-7.58.0.zip",
|
"package_url": "https://git-cloud.weboria.eu/Weboria/argus-wp-defence/releases/download/v7.66.0/argus-wordpress-defence-7.66.0.zip",
|
||||||
"sha256": "b140d997084875edafa67a4762f3f7ec5662c17cbf9670a024b092351e950a90",
|
"sha256": "a1d6796fbce70f75852b76d0a1f95c6ea535240cfae4de728d30ee042826344c",
|
||||||
"min_php": "7.4",
|
"min_php": "7.4",
|
||||||
"min_wp": "6.0",
|
"min_wp": "6.0",
|
||||||
"critical": false,
|
"critical": false,
|
||||||
"summary": "* Findings for events ARGUS already handled automatically -- a brute-force IP ban, a bad-bot\n auto-block -- now consistently say so, instead of occasionally still showing \"Nothing\n automatically\" after the action already happened.\n* If an automatic ban ever fails to save, ARGUS now raises its own finding about that failure\n instead of quietly treating the event as resolved.\n* Vulnerability Protection now recognises ARGUS WordPress Defence itself as a trusted, first-party\n component, instead of showing it as an unverified external plugin just because it isn't\n distributed through WordPress.org. A real vulnerability in ARGUS's own code is still detected\n and flagged just the same.",
|
"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": "1DvPQAaVW591I8ZNfz4ZVl0xTsJOOzRy1NCcrl3k6vizqbsrG4kvJd3O5lDLD23Q5VsFrUlM5BT/vatxN7soDQ=="
|
"signature": "4B4ZbdfBB7RcFMCt+YEWNJQfhspsGxsm9/RIv8p2O40b23Z+o/mwtGShV02wX66PsYUZlVfPoXnYbexMjHOGCw=="
|
||||||
}
|
}
|
||||||
|
|||||||
Reference in New Issue
Block a user