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 | ||
|
|
c8f8640e4c | ||
|
|
50336dfd90 | ||
|
|
85997bca02 | ||
|
|
3aa96c7b3e |
+6
-6
@@ -1,11 +1,11 @@
|
|||||||
{
|
{
|
||||||
"version": "7.61.0",
|
"version": "7.83.0",
|
||||||
"released_at": "2026-10-07T20:54:25+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.61.0/argus-wordpress-defence-7.61.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": "9b9cc0630470344a04c3440888919a885b916a057bb19f9d3eae3ab49a8bbc53",
|
"sha256": "0a706fa8564ca239a1d494533754f3aebeb9b68c23e94258c4cb1c7a02dfb67c",
|
||||||
"min_php": "7.4",
|
"min_php": "7.4",
|
||||||
"min_wp": "6.0",
|
"min_wp": "6.0",
|
||||||
"critical": false,
|
"critical": false,
|
||||||
"summary": "* A new registration Form Protection holds for your review can now actually be approved or\n rejected, from a new \"Pending Registration Reviews\" list on the Form Protection page -- Approve\n just closes the review, Reject stops that one account logging in without deleting it. Neither\n action adds the address to any trusted or blocked list on its own.\n* Every entry in Form Activity now has its own \"Trust address\" and \"Block address\" buttons, so you\n no longer need to go to the Firewall page to act on an address you see there.\n* Form Activity now shows plainly what actually happens to a held submission: for comments and new\n registrations, it's genuinely held and waiting for you; for Contact Form 7, WPForms and Gravity\n Forms, \"held for review\" already meant the submission was delivered (with its notification\n suppressed where possible) -- that's now stated outright instead of implied.\n* A request to a generic WordPress API address (used by the block editor and other core features,\n not by any contact form) no longer shows up in Form Activity labeled as a form submission.\n* When \"keep a short excerpt of the raw submission\" is switched on, that excerpt is now actually\n shown next to the matching entry in Form Activity -- and is automatically and permanently removed\n after a retention period you choose (24 hours, 72 hours, or 7 days), independently of how long the\n rest of your activity log is kept.",
|
"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": "cu5hJpT2hEHpqTHjD/ChLGdUV16tNv8D/17pc29dDNNy8Y6TholeZF/Gb71ARZ5GRVp3ZFJJNoYOdcSP57tADg=="
|
"signature": "qazQlKgliIyvPC+kLG2bJ8q8qJEOzpYlqHX6MEQNanyuZ1SYRmecVJCUeNrfuVCfWl6vT4Crk4FA2t9Oj8sjAQ=="
|
||||||
}
|
}
|
||||||
|
|||||||
Reference in New Issue
Block a user