Compare commits
| Author | SHA1 | Date | |
|---|---|---|---|
|
|
78dba72fad | ||
|
|
770acaf061 | ||
|
|
2ecef66d62 | ||
|
|
94e572214c | ||
|
|
da64bcaadb | ||
|
|
001bbefa3f | ||
|
|
ef6555a1e4 | ||
|
|
8832cee2da | ||
|
|
0c3ac9e463 |
+7
-7
@@ -1,11 +1,11 @@
|
||||
{
|
||||
"version": "7.73.0",
|
||||
"released_at": "2026-10-31T19:09:01+00:00",
|
||||
"package_url": "https://git-cloud.weboria.eu/Weboria/argus-wp-defence/releases/download/v7.73.0/argus-wordpress-defence-7.73.0.zip",
|
||||
"sha256": "34877adbeda02cef2046bb7f088c937b6d3d9c16a87596dfe65bca8d08be9300",
|
||||
"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",
|
||||
"min_php": "7.4",
|
||||
"min_wp": "6.0",
|
||||
"critical": true,
|
||||
"summary": "* WordPress core upgrades through ARGUS now use a safe, recoverable process: ARGUS first checks\n that your site is ready for the upgrade, verifies compatibility, takes a validated recovery\n backup, performs the upgrade, and automatically rolls back if a critical problem is detected\n afterwards. The upgrade button now gives a clear explanation if the safe upgrade process is not\n yet enabled on a site, rather than failing silently.\n* The \"Check upgrade readiness\" option now works correctly -- it runs a full compatibility and\n risk analysis and shows a report without making any changes to your site.",
|
||||
"signature": "Jx2wWfhIZ0UgHekgjBeUH8hBczvbI8smv+nlelScfzgBKUPRTPULYR7q1CZXK6H/nOzncb19GaxnJ66ZbJJ5AQ=="
|
||||
"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=="
|
||||
}
|
||||
|
||||
Reference in New Issue
Block a user