Compare commits

..
4 Commits
Author SHA1 Message Date
tech 19957d44b0 Update signed manifest to 7.55.0 2026-10-05 22:43:45 +00:00
tech 4054510acc Update signed manifest to 7.54.0 2026-10-05 17:12:23 +00:00
tech a0885f319a Update signed manifest to 7.53.0 2026-09-25 09:30:08 +00:00
tech a8cdbef65a Update signed manifest to 7.52.0 2026-09-23 09:51:35 +00:00
+6 -6
View File
@@ -1,11 +1,11 @@
{
"version": "7.51.0",
"released_at": "2026-09-19T16:44:43+00:00",
"package_url": "https://git-cloud.weboria.eu/Weboria/argus-wp-defence/releases/download/v7.51.0/argus-wordpress-defence-7.51.0.zip",
"sha256": "d423a2c0131a1a5b7a6b9761c7db98196466ba2d53aa6d97d0533d8d63bdc91c",
"version": "7.55.0",
"released_at": "2026-10-05T22:43:45+00:00",
"package_url": "https://git-cloud.weboria.eu/Weboria/argus-wp-defence/releases/download/v7.55.0/argus-wordpress-defence-7.55.0.zip",
"sha256": "b9fada51d586fe609fb51856b2835f819f9e43060232385be259a462fcbf5302",
"min_php": "7.4",
"min_wp": "6.0",
"critical": false,
"summary": "* Vulnerability Protection now investigates plugins that are not distributed through\n WordPress.org (private, premium, or vendor-hosted plugins) instead of simply reporting them as\n unchecked. It checks the plugin's own vendor identity, changelog, and available public\n vulnerability sources, and clearly shows what was checked, what was found, and how confident\n the result is.\n* Added a \"Check External Intelligence\" action on the Vulnerabilities page for these plugins, plus\n a dashboard summary of how much of your plugin inventory currently has complete vulnerability\n coverage.\n* Findings for these plugins are now created and cleared automatically as new information becomes\n available, the same way they already are for WordPress.org-distributed plugins.",
"signature": "Ed1qDtjAK+OCs7h4HkxCzxmCTTY8t1ONuwa+0UkDekhFawv/nVGDEfsLIVFAwE72s31abrF4itTOyRauA/fnBQ=="
"summary": "* The broader detection introduced in 7.54.0 now raises real alerts. ARGUS combines several\n independent pieces of evidence about the same file or address -- for example, a suspicious\n request closely followed by a new or changed file -- into one clearly-explained finding,\n instead of treating each piece as a separate, weaker signal.",
"signature": "+iOec3sJwqOzOn04OvTmXQIEa1dP1jS4mLpTdp+Z7s3lEDD/vYMZjoI7m/CaoTl5O+sVutTa9zl2XeAUX+Q0BA=="
}