Acunetix 360 On-Premises - v26.3.0
Improvements
- You can now specify the maximum number of rows (
LEN) in Discovery directly from the Settings menu - Invicti HTTP Requester can now be activated or deactivated from the Scan policy
- API responses for vulnerability issues now include the
IsAttackParameter, making it easier to pinpoint exactly which request parameter is vulnerable without additional investigation - The
UseHttpClientcan be activated in the Scan policy instead of account-based enablement - Resolved an issue where agents would terminate abruptly while archiving and finalizing long-running scans, ensuring scan results are fully preserved and processed regardless of scan duration
- Added detection for Advanced Custom Fields Extended (WordPress plugin)
- Improved detection logic of "Possible Password Transmitted over Query String" to better handle SPA applications using hash-based routing, reducing false positives in modern JavaScript authentication flows
- Aligned CVSS scores with the National Vulnerability Database
Resolved issues
- Scans no longer fail when running in restricted network environments - Passive Engine now retrieves host addresses more safely and reliably through the configured proxy, ensuring compatibility
- Resolved an issue where the VDB version remained outdated even after a successful update in the verifier mode, ensuring customers always see accurate and up-to-date version information
- Users who installed via silent install can now add targets without encountering licensing errors
- Resolved an issue where the AV Service configuration wasn't automated during silent installation, restoring a fully unattended install experience
- Resolved an issue where masking an API key in the URL with wildcards caused key mismatches during scans, resulting in 401/403 authentication errors
- Resolved an issue where WSDL file uploads were failing
Verify the Hash value for package integrity in Acunetix 360 on-premises
The hash value for the "26.3.0.zip" file is 658936B0054C1324E636E9FE68C68C8255D0F3FBDD4BD415F33ADBF1A24CED46.
You can verify the integrity of the file by checking its hash value using one of the outlined methods:
PowerShell (Windows):
Get-FileHash -Path "26.3.0.zip" -Algorithm SHA256
Command Prompt (Windows):
certutil -hashfile "26.3.0.zip" SHA256
Linux or macOS:
sha256sum "26.3.0.zip"