Compare commits
| Author | SHA1 | Date | |
|---|---|---|---|
|
|
78dba72fad | ||
|
|
770acaf061 | ||
|
|
2ecef66d62 | ||
|
|
94e572214c | ||
|
|
da64bcaadb | ||
|
|
001bbefa3f | ||
|
|
ef6555a1e4 | ||
|
|
8832cee2da | ||
|
|
0c3ac9e463 | ||
|
|
22b7a76a6e | ||
|
|
1544198d02 | ||
|
|
4b3e877127 | ||
|
|
8324647177 | ||
|
|
eec9b0e6f0 | ||
|
|
301e39dc66 | ||
|
|
aed69ceb6e | ||
|
|
82b525ca1e | ||
|
|
543bdd58d4 | ||
|
|
1ff0bdbeca | ||
|
|
09ac6a1fda | ||
|
|
2ce45b9c2d | ||
|
|
21ed592b8b | ||
|
|
cc56098488 | ||
|
|
8fa6153099 |
+6
-6
@@ -1,11 +1,11 @@
|
|||||||
{
|
{
|
||||||
"version": "7.65.0",
|
"version": "7.83.0",
|
||||||
"released_at": "2026-10-09T10:02:57+00:00",
|
"released_at": "2026-11-03T15:17:12+00:00",
|
||||||
"package_url": "https://git-cloud.weboria.eu/Weboria/argus-wp-defence/releases/download/v7.65.0/argus-wordpress-defence-7.65.0.zip",
|
"package_url": "https://git-cloud.weboria.eu/Weboria/argus-wp-defence/releases/download/v7.83.0/argus-wordpress-defence-7.83.0.zip",
|
||||||
"sha256": "b2962ccf1d5108af577f88e1e465476814f4e558bab5788c906b2ff033e57230",
|
"sha256": "0a706fa8564ca239a1d494533754f3aebeb9b68c23e94258c4cb1c7a02dfb67c",
|
||||||
"min_php": "7.4",
|
"min_php": "7.4",
|
||||||
"min_wp": "6.0",
|
"min_wp": "6.0",
|
||||||
"critical": false,
|
"critical": false,
|
||||||
"summary": "* Extended the 7.63.0/7.64.0 duplicate-finding fix to two more cases: a malware-scanner match, and\n a changed/new file that already has its own file-integrity finding, no longer also create a\n separate, duplicate \"suspicious behavior\" finding through Threat Correlation. A genuinely new,\n unconfirmed file change is unaffected and still raises a finding, as before.",
|
"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": "X3O9pKEAZcRYM30txJXzZdCbfL2tt9YDew9Jd4xVqNlQQojQkSQagbAGhZXiVAYocZr+yGJj/PI/noVo6qOZDg=="
|
"signature": "qazQlKgliIyvPC+kLG2bJ8q8qJEOzpYlqHX6MEQNanyuZ1SYRmecVJCUeNrfuVCfWl6vT4Crk4FA2t9Oj8sjAQ=="
|
||||||
}
|
}
|
||||||
|
|||||||
Reference in New Issue
Block a user