Report a security vulnerability
If you have found a weakness in Docuron, we want to hear it from you rather than from someone else. This page is the direct line: the form below reaches us without going through support, and we answer every report that describes a real issue.
What is in scope
- app.docuron.ai — the hosted service
- www.docuron.ai — this site
- The Docuron application itself, including an on-premise installation you operate yourself. If the finding is in your own installation, tell us the version.
Found something in a third party's installation of Docuron? Report it to us as well — a flaw in the product is ours to fix, wherever it runs.
What we will not act on
So that your time is not wasted: these are closed in one line, without a review.
- Scanner output with no demonstrated impact
- Missing headers, cookie flags, or a TLS / SPF / DMARC / DNSSEC grade, without a working attack
- Denial of service, load or resource-exhaustion testing
- Social engineering or phishing aimed at our people or our customers
- A public advisory for software we run, restated without showing it applies here
The ground rules — both ways
What we ask of you
- Use only your own test data. Do not read, copy or keep anyone else's documents — this is an accounting system, and those documents belong to real companies.
- Stop as soon as you have proof. Do not go further into the system than the finding needs.
- Give us a reasonable time to fix it before you publish.
What you get from us
- A human answer within 5 working days, and a word when the fix ships.
- Good-faith research that follows this page is authorised: we will not pursue legal action over it.
- Credit by name in our release notes, if you want it.
- We do not run a paid bounty programme. We say so here rather than let you find out after the work.
The report
Your report reached us.
We read every one of these ourselves. You will have an answer within 5 working days, at the address you gave.