Update signed manifest to 7.23.38

manifest.json

@@ -1,11 +1,11 @@
 {
-    "version": "7.23.30",
+    "version": "7.23.38",
-    "released_at": "2026-08-12T13:24:00+00:00",
+    "released_at": "2026-08-12T17:08:27+00:00",
-    "package_url": "https://git-cloud.weboria.eu/Weboria/argus-wp-defence/releases/download/v7.23.30/argus-wordpress-defence-7.23.30.zip",
+    "package_url": "https://git-cloud.weboria.eu/Weboria/argus-wp-defence/releases/download/v7.23.38/argus-wordpress-defence-7.23.38.zip",
-    "sha256": "81751849589995c4830915bb28a1b7983063571cfd3d728cac98457294e74703",
+    "sha256": "ca6d9a05d749f2483089bd2f6b9f58b322384f51a39c29fd90bb339c5bfc397f",
     "min_php": "7.4",
     "min_wp": "6.0",
     "critical": false,
-    "summary": "* Findings quality: routine, expected activity from legitimate plugins (like WooCommerce's cart/\n  checkout endpoints and Jetpack's public API) no longer shows up as a security issue just because\n  it doesn't require login -- ARGUS now recognizes it as normal.\n* Fixed a real false-positive: a legitimate WordPress core update could previously be flagged as a\n  suspicious file appearing or disappearing inside WordPress core. It's now correctly recognized as\n  an expected part of the update.\n* Fixed: repeated attacks matching the same firewall rule from different sources no longer create a\n  growing pile of near-identical findings -- they're now tracked as one finding with an occurrence\n  count, so your Findings list stays readable.\n* Fixed: a vulnerability finding (including \"WordPress core is out of date\") now automatically\n  clears itself once you actually update the affected plugin, theme, or WordPress core -- it no\n  longer stays open forever, or gets duplicated every time a newer version comes out.\n* Each finding now shows how confident ARGUS actually is (Confirmed, High confidence, Likely,\n  Suspicious, or Informational), so it's clear what's been verified versus what's an inference.\n* \"Resolve All Open\" is now \"Archive All Open\" -- same one-click way to clear your queue, but it no\n  longer implies everything was fixed; archived findings stay fully available in your history.\n* ARGUS now periodically checks its own health in the background (its files, database, scanner,\n  firewall, quarantine storage, and update mechanism) and can fix common problems automatically;\n  if something stays broken, you'll see it as a finding until it's verified resolved.\n* Two-factor authentication data is now fully removed when you uninstall the plugin.\n* Backups page: new charts showing your backup success/failure history and size trend over time.\n* License page: \"What's Included\" is now a simple, readable list instead of a dense table.",
+    "summary": "* Findings that ARGUS already handled automatically (a blocked WAF request, a blocked file\n  upload, blocked REST user-enumeration probing) no longer sit in \"Needs Attention\" -- the same\n  fix already shipped for brute-force login findings in 7.23.37 now covers every place this\n  happened. Existing findings from before this fix are cleaned up automatically on update, not\n  just new ones going forward.\n* The Protection Score on Overview is now color-coded (green/yellow/orange/red) instead of always\n  the same color regardless of how healthy your site actually is.\n* Backup integrity is now fully automatic end to end -- no \"Verify\" button to click; ARGUS\n  re-checks every backup's integrity once a day on its own, on top of the check it already does\n  the moment a backup is created.\n* The Backups page now displays properly on a phone.\n* New \"Purge Audit Log\" option on the Audit Log page, for clearing it manually at any time.",
-    "signature": "6p5dKzyfdivTHNN9qeMBQVVM9V3kb/fMWdTDvSj81Bp5wLuxOc/nVHerdoU2NMIleLjlhKGzQwpvt75shnabDw=="
+    "signature": "y9yWsjrUnm9datO0rsvoQRudPDAtG3e7fpnCjuPNWr33nTsz1js9l0PXiCer7otHeaL6QyDSV+Q0j+R6xZBhCQ=="
 }