Compare commits
| Author | SHA1 | Date | |
|---|---|---|---|
|
|
7d8aae8b8d | ||
|
|
fc9044d87b | ||
|
|
824e062747 | ||
|
|
9f4627c7c1 | ||
|
|
9647a4c776 | ||
|
|
0f19f0ab30 | ||
|
|
fb6cfa5664 | ||
|
|
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 |
+6
-6
@@ -1,11 +1,11 @@
|
||||
{
|
||||
"version": "7.83.0",
|
||||
"released_at": "2026-11-03T15:17:12+00:00",
|
||||
"package_url": "https://git-cloud.weboria.eu/Weboria/argus-wp-defence/releases/download/v7.83.0/argus-wordpress-defence-7.83.0.zip",
|
||||
"sha256": "0a706fa8564ca239a1d494533754f3aebeb9b68c23e94258c4cb1c7a02dfb67c",
|
||||
"version": "8.5.0",
|
||||
"released_at": "2026-11-15T12:39:35+00:00",
|
||||
"package_url": "https://git-cloud.weboria.eu/Weboria/argus-wp-defence/releases/download/v8.5.0/argus-wordpress-defence-8.5.0.zip",
|
||||
"sha256": "d8a21dd3b764d2a0edaa9d6f5b1e9ead551bbddf811fa5b8bde49770287bdc45",
|
||||
"min_php": "7.4",
|
||||
"min_wp": "6.0",
|
||||
"critical": false,
|
||||
"summary": "* Security fix: the custom login URL could be bypassed by percent-encoding the path (e.g. `/%77p-login.php` where `%77` is the letter \"w\") to reach the real login form instead of being blocked. All encoding variants, including double-encoded paths like `/%2577p-login.php`, are now normalised before any comparison.\n* Security fix: the custom login URL now works on all server configurations. Previously it relied on Apache mod_rewrite writing a rule to `.htaccess`, which silently does nothing on Nginx or without pretty permalinks. A PHP-level fallback now serves the login form for any server type.\n* Unauthorized access attempts to login and admin paths now show a deterrent page \u2014 displaying the visitor's IP address, timestamp, and a notice that the access has been logged \u2014 instead of a plain 404. This replaces the previous blank error response.\n* User enumeration protection: numeric author queries (`?author=1`) that redirect to `/author/username/` \u2014 a classic technique for discovering WordPress login names \u2014 are now blocked with a 404. The login username is never revealed.\n* User sitemaps removed: the `/wp-sitemap-users-1.xml` endpoint, which lists all registered user accounts, is now disabled. Regular page and post sitemaps are unaffected. Yoast SEO's user sitemap entries are also stripped.\n* Author archive pages are now sent with a `noindex,nofollow` header so search engines do not index or cache author slugs, which map directly to login usernames.\n* Author archive hard-block available (off by default): sites that do not need public author archives can now disable them entirely from Settings.",
|
||||
"signature": "qazQlKgliIyvPC+kLG2bJ8q8qJEOzpYlqHX6MEQNanyuZ1SYRmecVJCUeNrfuVCfWl6vT4Crk4FA2t9Oj8sjAQ=="
|
||||
"summary": "- Centralized progressive ban escalation policy: all automated ban paths now use a unified TTL ladder (L1 24h, L2 7d, L3 14d, L4 30d max) with a 90-day recurrence window, matching the WAD engine policy. Repeat offenders are banned for progressively longer durations regardless of which detection subsystem triggered the ban.",
|
||||
"signature": "VHnvrDa8mOvrQq+V4IbZqj8uyK8NjIT0To/NeuTAdZUwoHvGVZ7IYG9wtYNzydb3gWv61ln0lz0n/1DmfQYICw=="
|
||||
}
|
||||
|
||||
Reference in New Issue
Block a user