Compare commits

..
3 Commits
Author SHA1 Message Date
tech 78dba72fad Update signed manifest to 7.83.0 2026-11-03 15:17:13 +00:00
tech 770acaf061 Update signed manifest to 7.82.0 2026-11-03 11:07:18 +00:00
tech 2ecef66d62 Update signed manifest to 7.81.0 2026-11-03 10:58:36 +00:00
+6 -6
View File
@@ -1,11 +1,11 @@
{
"version": "7.80.0",
"released_at": "2026-11-02T22:23:14+00:00",
"package_url": "https://git-cloud.weboria.eu/Weboria/argus-wp-defence/releases/download/v7.80.0/argus-wordpress-defence-7.80.0.zip",
"sha256": "e438c17059dd73cb8dc765904d064154e357f04255896f741fc581cb1626a005",
"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": false,
"summary": "* Security fix: a class-loading timing bug in the must-use firewall loader caused every blocked request to be silently let through on sites running 7.71.3 to 7.79.1. The firewall appeared active but was not enforcing anything. This release fixes the loader so the firewall blocks correctly from the very first request.\n* Three editor false positives fixed: Classic Editor saves containing standard HTML elements (`<!--more-->`, `<img>`) were incorrectly banned and the editor's IP blocked. These have been live since August. Existing incorrect bans are cleared automatically on update.\n* The firewall now inspects JSON request bodies: a payload sent as `application/json` was previously scanned only as a raw string, allowing encoded sequences like `system(` to bypass every firewall rule. JSON values are now decoded and scanned individually.\n* PHP2Shell detection strengthened: six new rules catch additional code-execution patterns (dynamic callbacks, data-stream wrappers, write-and-execute chains, and server configuration injection) not covered before.\n* File upload guard now blocks `.phar`, `.user.ini`, `.htaccess`, `.htpasswd`, `php.ini`, `.php6`, and `.php8` \u2014 file types previously omitted.",
"signature": "rOHSNPYG/WhA1oMI8KSxZMKq0YupIka3Sqs3ksRB1mINGLk+4rZWnqGoyHik1Qw/oL15ApG6Dq1gomAgK6a1AA=="
"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=="
}