Compare commits
| Author | SHA1 | Date | |
|---|---|---|---|
|
|
94e572214c | ||
|
|
da64bcaadb | ||
|
|
001bbefa3f | ||
|
|
ef6555a1e4 | ||
|
|
8832cee2da | ||
|
|
0c3ac9e463 | ||
|
|
22b7a76a6e | ||
|
|
1544198d02 | ||
|
|
4b3e877127 | ||
|
|
8324647177 | ||
|
|
eec9b0e6f0 | ||
|
|
301e39dc66 | ||
|
|
aed69ceb6e | ||
|
|
82b525ca1e | ||
|
|
543bdd58d4 | ||
|
|
1ff0bdbeca | ||
|
|
09ac6a1fda |
+7
-7
@@ -1,11 +1,11 @@
|
||||
{
|
||||
"version": "7.69.0",
|
||||
"released_at": "2026-10-19T13:37:38+00:00",
|
||||
"package_url": "https://git-cloud.weboria.eu/Weboria/argus-wp-defence/releases/download/v7.69.0/argus-wordpress-defence-7.69.0.zip",
|
||||
"sha256": "d1c006de4e32d83d929285c6768633a4c1f21067560bb9a2c24280021e0d9014",
|
||||
"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",
|
||||
"min_php": "7.4",
|
||||
"min_wp": "6.0",
|
||||
"critical": true,
|
||||
"summary": "* Fixed a blank page after using Archive, Resolve, Acknowledge and the other actions on a finding\n once you had switched tabs or pages in Findings. You now return to the same tab and page, and a\n refused action is shown as an error instead of a success message.\n* The same threat arriving from many different addresses is now challenged automatically, instead of\n staying \"allowed\" however many addresses it came from. The thresholds are unchanged.\n* The \"Needs Attention\" tab in Findings is now called \"Critical & High\", which is exactly what it\n shows. Medium and low findings stay under \"Active\".\n* If ARGUS cannot apply a block or challenge, you now see a single clear finding about it instead of\n nothing, and a challenge that cannot be issued no longer shows a page nobody can complete.\n* Finding descriptions now say how many different sources a threat came from, rather than implying\n every request came from the most recent address.\n* Findings about a threat that was only \"allowed\" before this fix are closed automatically on update, with their evidence kept, and re-open if the threat comes back unchallenged.",
|
||||
"signature": "T78BKVQ08ouM8bqvKryZ3AN8SxAY+sySZfdBeCJA6jlsJMZO7GrHsnyRnyQ/lh2AcEUXiz9AiHr/syIIe5CDDw=="
|
||||
"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=="
|
||||
}
|
||||
|
||||
Reference in New Issue
Block a user