Compare commits
| Author | SHA1 | Date | |
|---|---|---|---|
|
|
1bb03b6c5c | ||
|
|
729c24a83c | ||
|
|
e95bc58ffc | ||
|
|
7cb4c1a8fc | ||
|
|
f20c35fbc5 | ||
|
|
d845e6a57d | ||
|
|
fbfa908695 | ||
|
|
39ef0c2f3f | ||
|
|
9a459b4644 | ||
|
|
342c2ee43f | ||
|
|
105abf4e24 | ||
|
|
d48beb9757 | ||
|
|
4a43572b15 | ||
|
|
20c46d3d26 | ||
|
|
74fdd42561 | ||
|
|
1e4806457e | ||
|
|
da9237171a | ||
|
|
904bf52960 | ||
|
|
8ea7b9f5be | ||
|
|
804a1aae58 | ||
|
|
76e585139e | ||
|
|
f871592d27 | ||
|
|
f1375d3d7d | ||
|
|
72fa8e8901 | ||
|
|
efa84723ee | ||
|
|
39616478c9 | ||
|
|
c1969d4293 | ||
|
|
524b893e65 | ||
|
|
303f31e869 | ||
|
|
20a2a84ee8 | ||
|
|
9127b06836 | ||
|
|
19cb788556 | ||
|
|
e52046437b |
+7
-7
@@ -1,11 +1,11 @@
|
|||||||
{
|
{
|
||||||
"version": "7.23.14",
|
"version": "7.23.48",
|
||||||
"released_at": "2026-08-10T10:42:30+00:00",
|
"released_at": "2026-08-13T10:52:35+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",
|
"package_url": "https://git-cloud.weboria.eu/Weboria/argus-wp-defence/releases/download/v7.23.48/argus-wordpress-defence-7.23.48.zip",
|
||||||
"sha256": "6b2365b173bd8e583a5d04021d205c773f927217b4870fc3ebff8c298c53367b",
|
"sha256": "50e2391f7f1f3cf36f0b7097c38b569ec12a0cc9bfe388329f767f5548edf543",
|
||||||
"min_php": "7.4",
|
"min_php": "7.4",
|
||||||
"min_wp": "6.0",
|
"min_wp": "6.0",
|
||||||
"critical": true,
|
"critical": false,
|
||||||
"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.",
|
"summary": "* Hardened login against username enumeration: a failed login attempt now always shows the same\n generic message, whether or not the username you tried actually exists on this site.",
|
||||||
"signature": "l3gHdqDlNbkuk88XuJpVOMiAbAMNVoht7lVJ0UgkgvcLgDUTmcnaYS9g6XoHqH6sPTkmLA6TL2SYe3d2d1NOCA=="
|
"signature": "hr5xP0f7D3U/BJ6a9nsGIyKtZFIrg7ljsENNaY1+oEpaA7iWCmEmFMvJRkQ6iMCAxBlMH4qIqaPWoGuI6qLaCw=="
|
||||||
}
|
}
|
||||||
|
|||||||
Reference in New Issue
Block a user