Compare commits

...
5 Commits
Author SHA1 Message Date
tech 5e682f6788 release: v7.88.0 2026-11-04 10:49:11 +00:00
tech 6045d150ca Update signed manifest to 7.87.0 2026-11-03 20:58:31 +00:00
tech 3d6fe5a100 Update signed manifest to 7.86.0 2026-11-03 20:47:39 +00:00
tech ea32a2e42e Update signed manifest to 7.85.0 2026-11-03 17:24:00 +00:00
tech 9f13bcabc4 Update signed manifest to 7.84.0 2026-11-03 16:46:15 +00:00
+6 -6
View File
@@ -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": "7.88.0",
"released_at": "2026-11-04T10:46:53Z",
"package_url": "https://git-cloud.weboria.eu/Weboria/argus-wp-defence/releases/download/v7.88.0/argus-wordpress-defence-7.88.0.zip",
"sha256": "0f7878b935ef9972c40ac3d49dc3717af66e69c59c0a0fd919d642913844281c",
"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": "* New: sensitive option monitor \u2014 blocks unauthorized changes to user registration settings and security keys; flags suspicious privilege escalations. * New: CVE virtual patching \u2014 receives signed, CVE-specific virtual patches from ANIS; blocks requests exploiting known vulnerable plugin versions. * New: behaviour engine \u2014 scores requests on entropy, encoding depth, request rate, user enumeration and failed login signals; auto-escalates to rate-limit or block. * New: WAF deep decoding \u2014 detects attacks hidden behind multiple layers of URL, HTML entity, base64 and hex encoding. * Fix: high-confidence SQL injection (hex-literal variant) was being allowed through instead of blocked. * Fix: settings IP exceptions were still triggering the auto-ban; challenge failures that could not be stored now fail closed; REST user enumeration in Monitor mode now recorded correctly. * New: enforcement_outcome field on findings.",
"signature": "5wXstYKwun6EVAYYO5Lx7Xmw8lUXNOMuQE/grZfE3G2qZAMFSdL+3bVGXkS177rieg2jXvOeGeKZfAkdizFzCQ=="
}