A security review of a live billing platform, and the two findings a stranger could use
Security & Compliance
The challenge
A commercially licensed multi-tenant billing platform was carrying real customers, real invoices and real money, and the operator wanted a roadmap of new features. The question they asked first was whether the controls underneath it were sound enough to build on.
What we built
We reviewed the application source, its configuration, its routing, a schema of 264 tables and 22 bundled modules, and recorded 33 findings — nine critical, eleven high, nine medium and four concerning readiness to develop safely. Two of the critical ones needed no account, no credentials and no knowledge of the business: one let a stranger run commands on the server, the other meant no subscription payment was ever confirmed with the payment provider, so any customer with a login could activate any plan without paying.
The result
The review gave the operator a decision they could actually take: not a list of things that might be improved, but a count of what was exploitable that day and by whom. The remediation is scoped as a single programme rather than a menu, because the cheap findings are the gaps the expensive ones travel through — and sequenced so the two that need no account close first.