Update signed manifest to 7.23.41

manifest.json

@@ -1,11 +1,11 @@
 {
-    "version": "7.23.14",
+    "version": "7.23.41",
-    "released_at": "2026-08-10T10:42:30+00:00",
+    "released_at": "2026-08-12T19:11:52+00:00",
-    "package_url": "https://git-cloud.weboria.eu/Weboria/argus-wp-defence/releases/download/v7.23.14/argus-wordpress-defence-7.23.14.zip",
+    "package_url": "https://git-cloud.weboria.eu/Weboria/argus-wp-defence/releases/download/v7.23.41/argus-wordpress-defence-7.23.41.zip",
-    "sha256": "6b2365b173bd8e583a5d04021d205c773f927217b4870fc3ebff8c298c53367b",
+    "sha256": "9fb4dfb0d664506f123bba37cacb4c2c132974eb0b559245c01b87d67dbabb49",
     "min_php": "7.4",
     "min_wp": "6.0",
-    "critical": true,
+    "critical": false,
-    "summary": "* Fixed a serious bug: the Firewall could block ordinary visitors just for arriving from an\n  everyday link -- for example, a link shared on Facebook, whose own redirect URL happened to\n  match a pattern the Firewall treated as suspicious. The underlying cause was broader than that\n  one case: 132 of the Firewall's 137 protection rules were checking a visitor's Referer,\n  User-Agent, and X-Forwarded-For information -- values a visitor doesn't control -- when they\n  should only ever have been checking what a visitor actually submits (search terms, form fields,\n  comments, and similar). Those three values are now excluded everywhere except the handful of\n  rules that specifically need them (Log4Shell-style attacks are delivered through exactly those\n  values, so detection there is unchanged). No settings change needed; this takes effect\n  automatically.",
+    "summary": "* Behind-the-scenes groundwork for a future update -- no visible changes in this release.",
-    "signature": "l3gHdqDlNbkuk88XuJpVOMiAbAMNVoht7lVJ0UgkgvcLgDUTmcnaYS9g6XoHqH6sPTkmLA6TL2SYe3d2d1NOCA=="
+    "signature": "2ty1yu2j10iB90YG3LIum5eJbILFruO0jPhqIj74ZF2OpEPGCftzZEmDtR+0KD4A4IgfpzJDCl4eFOnTDi3oBg=="
 }