Acunetix Reporting,
With the Request That Proves It
Import Acunetix XML reports into Neuron and every vulnerability lands with the request and response that prove it, mapped to its endpoint. Acunetix report import.
Import Once. Report From One Place.
Acunetix finds the SQL injection and records the exact request that triggered it. Most of that proof is gone by the time the issue reaches a report. Neuron imports the Acunetix XML and keeps it attached.
Each scanned URL becomes a web app with its host and port, and every affected path and parameter becomes an endpoint and param. Each vulnerability lands in the Scan Issues queue with its severity, CVSS 3 score, CWE and CVE IDs, description, impact, recommendation, and references, and every place it fired keeps its own details, request, and response.
Anything you already marked as a false positive in Acunetix stays out. Upload the XML in the browser or run neuron import on it.
$ neuron import acme-portal-acunetix.xml Importing into Acme Web App Q4 acunetix: 1 web app, 63 endpoints, 41 params✓ 29 scan issues queued for triage- 13:41 Finding SQL Injection in /api/orders (id)
- 13:27 Import Acunetix: 1 web app, 29 scan issues
- 13:26 Command neuron import acme-portal-acunetix.xml
- 11:50 Import Burp Suite: 412 requests, 1 web app
Why Acunetix Reporting Takes So Long
A DAST scan of one application can report the same vulnerability on dozens of paths and parameters. Acunetix's own reports are designed for Acunetix users rather than your client, and copying out of them strips the raw HTTP that makes a finding reproducible.
So testers rebuild every finding by hand: copy the vulnerability name, list each affected URL and parameter, screenshot the request, then replay it to be sure it is real.
The scanner's verified and possible markers get lost along the way, and with them the difference between a proven issue and a lead.
Everything Acunetix Produces, On the Engagement
Import Acunetix output from the browser or with neuron import, and it lands the moment the import finishes.
Web Apps, Endpoints, and Params
Each scanned URL as a web app with its host and port, and every affected path and parameter as an endpoint and param.
One Issue per Vulnerability
Each Acunetix vulnerability as one scan issue, with every path and parameter it was found on listed beneath it.
Request and Response
The HTTP request and response Acunetix captured for each affected resource, opened with Show evidence right under the row.
Severity, CVSS, CWE, and CVE
Acunetix severity, the CVSS 3 base score where present, and CWE and CVE IDs for every vulnerability.
Verified and Possible
Acunetix's own verified and possible markers, kept as attributed scanner detail so a lead never reads like a confirmed finding.
Impact and Recommendation
The description, impact, recommendation, and reference links from the report, attached to the issue for context.
How to Import Acunetix Results
- 01
Export the scan as XML
From Acunetix Standard or Premium, export the finished scan as XML, the format whose root element is ScanGroup. It keeps the details, request, and response for every vulnerability.
- 02
Import it in the browser
In the engagement, choose Import, then Acunetix. Set Minimum Severity, choose whether to create web apps and hosts and ports, and click Start Import.
- 03
Or import it from the terminal
neuron import recognises the Acunetix format from its content. Add --ssh and an absolute path to read the file from the box it was exported to.
$ neuron import acme-portal-acunetix.xml - 04
Verify against the evidence
Open each issue, use Show evidence to read the request and response, confirm or dismiss it, and promote confirmed issues into findings.
Your Infrastructure. Your Data.
Neuron is self-hosted. Import Acunetix results from the browser or the CLI and they land on your own server, inside your network. Scan data never passes through a third-party cloud.
From Acunetixto the Final Report
Promoted Acunetix issues carry their affected endpoints and parameters into the finding, together with the request and response that reproduce each one.
Because the web app, endpoints, and params now exist in the engagement, traffic you send later from Burp Suite, ZAP, or Caido lands against the same application.
Rescan for the retest and import the new XML. Fixed vulnerabilities are marked Fixed, and the rest update without losing your triage decisions.
Acunetix Integration FAQ
The questions teams ask most about Acunetix and Neuron.
How do I import Acunetix results into a pentest report?
Export the Acunetix scan as XML and import it into the Neuron engagement, in the browser or with neuron import. Each vulnerability becomes a scan issue with its affected endpoints and the request and response that prove it, ready to promote into a finding.
Which Acunetix export format does Neuron accept?
The Acunetix XML export from Standard or Premium, the one whose root element is ScanGroup. The Neuron CLI recognises it from its content, so neuron import needs no --source.
Does the Acunetix request and response come across?
Yes. Every affected path and parameter keeps the HTTP request and response Acunetix captured, plus its details text. Show evidence opens them directly under the resource in the Scan Issues queue.
Are Acunetix false positives imported?
No. Items marked as false positives in the Acunetix export are skipped, so the triage queue starts with only what Acunetix still considers live.
What happens to Acunetix verified and possible markers?
They are kept as Acunetix's own, attributed scanner detail on the issue. Neuron never turns them into a confirmed status. An issue is only confirmed when a tester marks it so.
Does Acunetix data leave our network?
No. Neuron is self-hosted, so the report, the request and response evidence, and every finding stay on your own Neuron server.
More Neuron Integrations
Burp Suite Reporting and Findings Import
Web TestingZAP Reporting and OWASP ZAP Alert Import
Web TestingCaido Reporting and HTTP History Import
Web TestingOpenAPI and Swagger Import for API Pentests
Web TestingNuclei Scan Reporting and Import
Web Testingffuf Reporting and Content Discovery Logging
Web TestingNikto Reporting and Output Import
Web TestingInvicti and Netsparker Report Import
Web TestingReady to Transform Your Security Practice?
See how Neuron helps security teams replace fragmented tools with a single platform for offensive security, bringing structure, visibility, and consistency to every engagement.
Platform