Compare commits
| Author | SHA1 | Date | |
|---|---|---|---|
|
|
20a2a84ee8 | ||
|
|
9127b06836 | ||
|
|
19cb788556 | ||
|
|
e52046437b |
+7
-7
@@ -1,11 +1,11 @@
|
||||
{
|
||||
"version": "7.23.14",
|
||||
"released_at": "2026-08-10T10:42:30+00:00",
|
||||
"package_url": "https://git-cloud.weboria.eu/Weboria/argus-wp-defence/releases/download/v7.23.14/argus-wordpress-defence-7.23.14.zip",
|
||||
"sha256": "6b2365b173bd8e583a5d04021d205c773f927217b4870fc3ebff8c298c53367b",
|
||||
"version": "7.23.18",
|
||||
"released_at": "2026-08-10T14:14:25+00:00",
|
||||
"package_url": "https://git-cloud.weboria.eu/Weboria/argus-wp-defence/releases/download/v7.23.18/argus-wordpress-defence-7.23.18.zip",
|
||||
"sha256": "757e47dc84fa8f113dd1e2dc0a0cb1436a98c37286b0fcf4835a87f419953b57",
|
||||
"min_php": "7.4",
|
||||
"min_wp": "6.0",
|
||||
"critical": true,
|
||||
"summary": "* Fixed a serious bug: the Firewall could block ordinary visitors just for arriving from an\n everyday link -- for example, a link shared on Facebook, whose own redirect URL happened to\n match a pattern the Firewall treated as suspicious. The underlying cause was broader than that\n one case: 132 of the Firewall's 137 protection rules were checking a visitor's Referer,\n User-Agent, and X-Forwarded-For information -- values a visitor doesn't control -- when they\n should only ever have been checking what a visitor actually submits (search terms, form fields,\n comments, and similar). Those three values are now excluded everywhere except the handful of\n rules that specifically need them (Log4Shell-style attacks are delivered through exactly those\n values, so detection there is unchanged). No settings change needed; this takes effect\n automatically.",
|
||||
"signature": "l3gHdqDlNbkuk88XuJpVOMiAbAMNVoht7lVJ0UgkgvcLgDUTmcnaYS9g6XoHqH6sPTkmLA6TL2SYe3d2d1NOCA=="
|
||||
"critical": false,
|
||||
"summary": "* Added a way to download your MFA backup codes as a file right after they're generated, so you\n don't have to copy them down by hand. You can optionally protect the file with your own\n passphrase -- it's encrypted in your browser before saving, and a matching offline tool (linked\n from the same page) lets you read it back later even if you can't reach your site's admin area.\n* Fixed an edge case in Safe Mode (the wp-config.php recovery switch) where a fresh security event\n happening while Safe Mode was on could still block the request -- Safe Mode now reliably means no\n blocking at all, matching what it has always said it does.",
|
||||
"signature": "oLZpuEEZu+3hUkmR19i2ISNbeCycjhDO/aZ2ZwpxlBbTvAOI8LJh9+rc6G6Tnd404ttvaBR0nl6Y3QWrLYFBDw=="
|
||||
}
|
||||
|
||||
Reference in New Issue
Block a user