Compare commits
| Author | SHA1 | Date | |
|---|---|---|---|
|
|
26dd83e8bc | ||
|
|
c2eae8801b | ||
|
|
a9f7b6ddf9 | ||
|
|
1a959fcdbb | ||
|
|
81d011d56a | ||
|
|
510eab15b3 | ||
|
|
95cb325dd6 | ||
|
|
6bc43378e2 | ||
|
|
99de067d89 | ||
|
|
85bc2b0123 | ||
|
|
830bc5b38a | ||
|
|
407ae0a5f9 | ||
|
|
4d738638a7 | ||
|
|
7c22b85cdf | ||
|
|
027bdc5d06 | ||
|
|
dad8018345 | ||
|
|
91f73b55b0 | ||
|
|
3d2424a027 | ||
|
|
30acc5c9fe | ||
|
|
ada915a068 | ||
|
|
743bf0c7d8 | ||
|
|
5e682f6788 | ||
|
|
6045d150ca | ||
|
|
3d6fe5a100 | ||
|
|
ea32a2e42e | ||
|
|
9f13bcabc4 | ||
|
|
78dba72fad | ||
|
|
770acaf061 | ||
|
|
2ecef66d62 | ||
|
|
94e572214c | ||
|
|
da64bcaadb | ||
|
|
001bbefa3f | ||
|
|
ef6555a1e4 | ||
|
|
8832cee2da |
+6
-6
@@ -1,11 +1,11 @@
|
|||||||
{
|
{
|
||||||
"version": "7.74.0",
|
"version": "8.2.4",
|
||||||
"released_at": "2026-11-01T10:06:45+00:00",
|
"released_at": "2026-11-09T16:21:53+00:00",
|
||||||
"package_url": "https://git-cloud.weboria.eu/Weboria/argus-wp-defence/releases/download/v7.74.0/argus-wordpress-defence-7.74.0.zip",
|
"package_url": "https://git-cloud.weboria.eu/Weboria/argus-wp-defence/releases/download/v8.2.4/argus-wordpress-defence-8.2.4.zip",
|
||||||
"sha256": "8aeff5ccb8dcb4d8565aa1d5df10b096badc80ca9521949cbf89493c191520f0",
|
"sha256": "6b60084ce3acd6142144e16eecb330adab40f59f60e1584c5247abe823a29d60",
|
||||||
"min_php": "7.4",
|
"min_php": "7.4",
|
||||||
"min_wp": "6.0",
|
"min_wp": "6.0",
|
||||||
"critical": false,
|
"critical": false,
|
||||||
"summary": "* Requests for backup files (.bak, .sql, .tar.gz, etc.) and sensitive dotfiles (.git/config,\n .env, .ssh/id_rsa, etc.) are now blocked immediately rather than only monitored. These patterns\n have no legitimate use on a WordPress site and were previously classified as medium-severity,\n which meant they could slip through when spread across many different source addresses.\n Existing open findings for these patterns are automatically re-classified as high-severity.",
|
"summary": "* Improvement: plugin update now triggers automatic historical security reanalysis \u2014 all existing findings, IPs, bans, and cross-site correlation records are reassessed using the latest detection rules.\n* Fix: trusted proxy auto-detection now covers Cloudflare and RFC 1918 reverse proxies; historical findings caused by misconfigured proxy trust are automatically resolved without banning legitimate infrastructure.\n* Fix: backup schedule hour and minute settings are now correctly preserved after save.",
|
||||||
"signature": "2HkDgBA5cxqQAtRQhhuM+y/M8oOsxeCWbTBeoPr1qTRfMj+5JPHJ3HUUm2mVbRWUjZZqo8XB+tdvKEhw25nYDQ=="
|
"signature": "U/cegjBEK8YNbY/Dwyfzdpbg0D7k0273RJLtnewBOY88X6XtUvdePtXQagRsVKzYW55Do7F3CNz9QHsbzgbnCA=="
|
||||||
}
|
}
|
||||||
|
|||||||
Reference in New Issue
Block a user