Compare commits
| Author | SHA1 | Date | |
|---|---|---|---|
|
|
2ecef66d62 | ||
|
|
94e572214c | ||
|
|
da64bcaadb | ||
|
|
001bbefa3f | ||
|
|
ef6555a1e4 | ||
|
|
8832cee2da | ||
|
|
0c3ac9e463 | ||
|
|
22b7a76a6e | ||
|
|
1544198d02 | ||
|
|
4b3e877127 | ||
|
|
8324647177 | ||
|
|
eec9b0e6f0 | ||
|
|
301e39dc66 | ||
|
|
aed69ceb6e | ||
|
|
82b525ca1e | ||
|
|
543bdd58d4 | ||
|
|
1ff0bdbeca | ||
|
|
09ac6a1fda | ||
|
|
2ce45b9c2d | ||
|
|
21ed592b8b | ||
|
|
cc56098488 | ||
|
|
8fa6153099 | ||
|
|
c8f8640e4c | ||
|
|
50336dfd90 |
+6
-6
@@ -1,11 +1,11 @@
|
||||
{
|
||||
"version": "7.63.0",
|
||||
"released_at": "2026-10-08T06:48:51+00:00",
|
||||
"package_url": "https://git-cloud.weboria.eu/Weboria/argus-wp-defence/releases/download/v7.63.0/argus-wordpress-defence-7.63.0.zip",
|
||||
"sha256": "4185f4d090d6edaafe86952c017bc60b7673dd4b39402740872e1b8167a1abbb",
|
||||
"version": "7.81.0",
|
||||
"released_at": "2026-11-03T10:58:35+00:00",
|
||||
"package_url": "https://git-cloud.weboria.eu/Weboria/argus-wp-defence/releases/download/v7.81.0/argus-wordpress-defence-7.81.0.zip",
|
||||
"sha256": "ea5565d231a2d20ff1b4d7a65bd27b7e2065d47cf1a6a148eee4a337d6ed2a59",
|
||||
"min_php": "7.4",
|
||||
"min_wp": "6.0",
|
||||
"critical": false,
|
||||
"summary": "* Fixed a real gap in the 7.62.0 Monitor Mode fix: a bot ban or other already-fully-handled event\n could still turn into a second, separate \"suspicious behavior\" finding through Threat\n Correlation, duplicating what the Monitor Mode rollup (or the ban itself) had already covered.\n This no longer happens -- genuinely correlated, multi-signal findings are completely unaffected.",
|
||||
"signature": "PWMBZPER9IETw5Vjdvdly578k5fTmd8BQDCMFdejYQJhd8ShkOmni/hmXVQQ4ap6LAiXhXJd7gfkFincqq08Aw=="
|
||||
"summary": "* Security fix: multipart file uploads submitted directly to a plugin endpoint (bypassing WordPress's own upload handler) were not inspected by the firewall. Executable-named files (.php, .phar, .htaccess, .user.ini and similar) sent this way are now blocked before they reach any plugin.\n* Security fix: the firewall's request scanner could strip real backslashes from form field values when running at the earliest stage (before WordPress's own input handling had run), potentially masking an attack pattern that relied on them. The scanner now preserves those characters correctly at that stage.",
|
||||
"signature": "cXyMUO3RAiXhL2Uu8BrurZVro93pAp2vYyf4riSlwewYe60pcXNcbsvlFaly0HthSCpDxOZsLfZiSXc9tDMgAQ=="
|
||||
}
|
||||
|
||||
Reference in New Issue
Block a user