Compare commits
| Author | SHA1 | Date | |
|---|---|---|---|
|
|
770acaf061 | ||
|
|
2ecef66d62 | ||
|
|
94e572214c | ||
|
|
da64bcaadb | ||
|
|
001bbefa3f | ||
|
|
ef6555a1e4 | ||
|
|
8832cee2da | ||
|
|
0c3ac9e463 | ||
|
|
22b7a76a6e | ||
|
|
1544198d02 | ||
|
|
4b3e877127 | ||
|
|
8324647177 | ||
|
|
eec9b0e6f0 | ||
|
|
301e39dc66 | ||
|
|
aed69ceb6e | ||
|
|
82b525ca1e | ||
|
|
543bdd58d4 | ||
|
|
1ff0bdbeca | ||
|
|
09ac6a1fda |
+7
-7
@@ -1,11 +1,11 @@
|
|||||||
{
|
{
|
||||||
"version": "7.69.0",
|
"version": "7.82.0",
|
||||||
"released_at": "2026-10-19T13:37:38+00:00",
|
"released_at": "2026-11-03T11:07:17+00:00",
|
||||||
"package_url": "https://git-cloud.weboria.eu/Weboria/argus-wp-defence/releases/download/v7.69.0/argus-wordpress-defence-7.69.0.zip",
|
"package_url": "https://git-cloud.weboria.eu/Weboria/argus-wp-defence/releases/download/v7.82.0/argus-wordpress-defence-7.82.0.zip",
|
||||||
"sha256": "d1c006de4e32d83d929285c6768633a4c1f21067560bb9a2c24280021e0d9014",
|
"sha256": "c62a4400903a29b531c2b0b4336ade3039abc033794b9fd9c81238a96aa3a9a6",
|
||||||
"min_php": "7.4",
|
"min_php": "7.4",
|
||||||
"min_wp": "6.0",
|
"min_wp": "6.0",
|
||||||
"critical": true,
|
"critical": false,
|
||||||
"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.",
|
"summary": "* Security fix: a firewall rule that detects Windows command injection (intended for shell-like payloads) was incorrectly triggering on ordinary English phrases like \"Search & replace\" or \"Find & update\", banning the editor's IP. The rule now correctly ignores standalone ampersands in prose text while continuing to detect real injection patterns that use shell operators.",
|
||||||
"signature": "T78BKVQ08ouM8bqvKryZ3AN8SxAY+sySZfdBeCJA6jlsJMZO7GrHsnyRnyQ/lh2AcEUXiz9AiHr/syIIe5CDDw=="
|
"signature": "ThkU6fJAl0HrSo+/0opMjYXjy3Zg0T0/uOlwgTvluhpM9OFM6/SWXDqxBzmcnFsM98yV3LKn7Jz8xhxLeS/tCw=="
|
||||||
}
|
}
|
||||||
|
|||||||
Reference in New Issue
Block a user