# WHMCS Security Audit

> WHMCS version, admin access, files, modules, hooks, API keys, cron and server reviewed, with a severity-rated report.

WHMCS security audit covering patches, admin access, 2FA, file permissions, configuration.php, API keys, modules, hooks, cron, server and backups, with a re-test.

- **Price:** Starting at $149
- **Billing:** One-time, fixed scope
- **Category:** Security
- **Quote turnaround:** Fixed-price quote within 24 hours
- **Start a project:** https://whmcspilot.com/start-project
- **Details:** https://whmcspilot.com/services/whmcs-security-audit
- **Last updated:** 2026-11-03

## Overview

A WHMCS security audit is a structured review of one WHMCS install and the server under it, ending in a written report that ranks every weakness found by severity. Owners order it before trouble starts, after inheriting an install from someone else, or after a staff member with admin access leaves. The audit starts at $149.

## When an audit is worth doing

- You took over a WHMCS install and do not know what was added to it over the years
- Modules or themes were bought from sources you can no longer vouch for
- Someone with full admin or server access has left the business
- Your payment provider or a customer has asked how you protect account data
- WHMCS has not been updated for several patch releases

## What we check

### Application

- **Version and patches.** Your WHMCS release compared with current security releases, and whether the latest patch set is applied.
- **Admin access.** Admin directory name, IP restrictions, every admin user and role, last login dates and any shared logins.
- **Two-factor authentication.** Whether it is enforced for staff and offered to clients.
- **configuration.php.** File permissions, database user privileges, and whether copies of the file or the encryption hash sit in backups, Git repositories or public folders.
- **API credentials.** Role, permissions and IP restriction for each set, and which ones nobody uses any more.
- **Modules, addons and themes.** Each listed with its version, whether it is still maintained, and whether it came from a legitimate source. Nulled modules are a well-known route for backdoors.
- **Hooks.** Every file in includes/hooks read line by line, because one unknown hook can quietly copy passwords or card details at each login or checkout.
- **Gateway settings.** Whether card numbers are stored locally, and whether callback files match what the gateway vendor shipped.

### Files and server

- **Permissions and writable folders.** Attachments, downloads, templates\_c and crons outside the web root, with no world-writable directories.
- **File integrity.** Core files compared with a clean copy of your exact WHMCS version to spot changed or added files.
- **Cron.** How it runs, as which user, and whether the crons folder can be reached from the web.
- **Server hardening.** PHP version and risky functions, SSH and control panel access, open ports and TLS settings.
- **Backups.** Whether they exist off the server, are encrypted, and have ever been restored.
- **Logs.** Admin and activity logs searched for unfamiliar IPs, bursts of failed logins and recent configuration changes.

## What you receive

1. A written report with each finding rated critical, high, medium or low, what it means in plain language, and how to fix it.
2. Low-risk fixes applied during the audit with your approval, such as deleting an unused admin, tightening permissions or restricting an API credential.
3. A quote for the larger fixes, or step-by-step instructions if your own team will handle them.
4. A re-test once fixes are in place, with the report updated to show what is closed.

## What a finding looks like

Each item in the report follows the same pattern, so it can be handed straight to whoever fixes it. For example: *High. The API credential labeled "integration" has full permissions and no IP restriction. Anyone holding its secret can add admin-level changes from anywhere. Fix: assign a role limited to the actions your integration uses and restrict it to your application server's IP.* Findings are grouped by severity, so you can close the critical ones the same day.

## How we work on a live install

Checks are read-only unless you approve a change. Nothing is deleted during the audit, even a file that looks malicious; it is copied for analysis and reported first, so evidence is kept and you decide what happens next.

## Timeline

Auditing a single install usually takes two to four business days from receiving access to delivering the report. The re-test happens whenever your fixes are done, whether that is the same week or a month later.

## Pricing

ScopePriceOne WHMCS install and its server: report, quick fixes and re-testFrom $149Several installs, or servers hosting many customer sitesFixed quoteRemediation of larger findingsFixed quote, or $65/hour

## If you suspect you have already been hacked

An audit assumes the install is healthy and looks for weak points. If you see signs of compromise, such as admin users you did not create, changed gateway settings or customers receiving invoices you never sent, put that in your first [message](/contact). Incident response runs in a different order, with containment before investigation, and the scope changes accordingly.

## Typical next steps after the report

Findings often lead to [2FA setup](/services/whmcs-2fa-setup) for staff and clients, [firewall and brute-force rules](/services/whmcs-firewall) in front of WHMCS, or [backup and disaster recovery](/services/whmcs-backup-setup) where restores have never been tested. To keep watching for exploits between audits, look at the [WHMCS Security module](/modules/whmcs-security).

## What's included

- WHMCS version and patch level against current security releases
- Admin directory, IP restrictions, users, roles and last logins reviewed
- 2FA enforcement checked for staff and clients
- configuration.php permissions, database privileges and stray copies
- API credential roles and IP restrictions
- Modules, addons and themes checked for maintenance status and origin
- Line-by-line review of every hook file
- Core file integrity compared with a clean copy of your version
- Server, cron, backup and log review
- Severity-rated written report, quick fixes and a re-test

## Business outcomes

- A clear, ranked list of what to fix first instead of a vague worry
- Leftover admin accounts and unused API keys are found and closed
- Unknown hooks or modified core files are spotted before they cause damage
- You learn whether your backups would actually save you
- The re-test shows what has been closed, in writing

## Frequently asked questions

### How much does a WHMCS security audit cost?

From $149 for one WHMCS install and its server, including the report, quick fixes and a re-test. Several installs or large shared servers are quoted after the scoping call.

### Do you need root access?

Root or sudo access allows the most complete server review, but it is not required. With control panel and WHMCS admin access only, we audit the application and note which server checks could not be run.

### Will the audit take WHMCS offline?

No. The checks are read-only, and any fix that could affect customers is applied at a time you agree.

### Is this a penetration test?

No. It is a configuration and code review of your install and server, not an attempt to break in from outside. If you need a formal penetration test, use a specialist firm, and our report gives them a useful starting point.

### How often should WHMCS be audited?

Once a year is a sensible minimum, plus after staff changes, after buying modules from a new vendor and after a major WHMCS upgrade.

### What do I need to provide?

Full WHMCS admin access, server access over SSH or your control panel, and a list of the modules you know you installed. Anything we find that is missing from your list gets extra attention.
