Skip to content

Creating a WHM reseller and the ACL template that actually scopes them

Reseller creation is a two-step dance — make the user, then bolt on an ACL list. Defaults are dangerously broad; a tightened ACL template per reseller class saves trouble later.

A new reseller is added through the WHM interface, the operator picks “create with default ACL”, and the reseller is now able to view every account on the server, run package operations on accounts they don’t own, and read logs that belong to other resellers. The default ACL list defaultacls was last set up for a single-tenant box in 2011 and nobody trimmed it. Reseller security in WHM is exactly as good as the ACL template you assigned at create time.

What’s happening

A WHM reseller is a cPanel user with the reseller flag set plus an entry in /var/cpanel/resellers and /var/cpanel/resellers-nameservers. The ACL list controls which WHM functions they can call against accounts they own. The default defaultacls template is permissive — among other things, it grants list-accts globally, all-acl on owned accounts, and kill-acct (terminate) without confirmation gates. For a real reseller business, you want a tighter template that grants enough to run a customer base, blocks anything that touches other resellers, and forces sensitive actions through a manual root-only path.

How to verify

Inspect the available ACL lists and what each one grants:

whmapi1 listacls
whmapi1 get_reseller_acl_list user=acmevpn
ls /var/cpanel/acllists/
cat /var/cpanel/acllists/defaultacls
tail -f /usr/local/cpanel/logs/access_log | grep saveacllist

The listacls output enumerates every ACL keyword in the system. get_reseller_acl_list shows which are granted to a specific reseller. The file under /var/cpanel/acllists/ is the on-disk template — the source of truth WHM reads when applying an ACL list to a reseller.

The fix

  1. Create at least three ACL templates for the reseller classes you actually have: reseller-standard (own-account read/write, no terminate, no IP changes), reseller-power (adds terminate but with logging hook), reseller-readonly (audit accounts and call billing teams).
  2. Build the templates by copying defaultacls and stripping the ACLs you don’t want: cp /var/cpanel/acllists/defaultacls /var/cpanel/acllists/reseller-standard, edit, save, and the new template appears in WHM.
  3. Forbid all-acl from any template you give to actual resellers. It future-proofs against new ACLs cPanel adds — and grants them automatically. Always whitelist; never grant all-acl.
  4. Tie ACL assignment to reseller creation in your provisioning script — whmapi1 setacls reseller=acmevpn acllist=reseller-standard immediately after creating the user. Never leave the default ACL in place even for a few minutes.

Multi-reseller WHM environments benefit from the kind of role-based access scaffolding Stack Harbor’s agency partner practice builds into onboarding, so every new reseller starts with the right blast radius.