💡 Feature: Add tables for whitelist / blacklist management

[josh-jday]

Control Panel › Name

cPanel

Category

🗔 Cosmetic / Web Interface

Feature Description

Enhanced WHM Web UI for IP Whitelist & Blacklist Management
Overview

While IP whitelist and blacklist management is currently functional via the CLI, the existing web interface is quite minimal. A more fully featured, table-based WHM UI would significantly improve day-to-day usability, visibility, and safety when managing IP rules.
Proposed Enhancements

1. Table-Based IP Management Interface
   Dedicated Whitelist and Blacklist views (tabs or segmented control)
   Searchable, filterable, and sortable table
   Support for both IPv4 and IPv6, including CIDR ranges
2. Table Columns
   IP address / CIDR range
   Description or reason (label)
   Added by (user/process)
   Date added
   Expiry / TTL (if applicable)
   Status (active / expired)
   Optional: last matched / hit count
3. Add & Edit IP Rules
   Inline or modal-based add/edit flows
   Strong input validation for IPs and CIDRs
   Duplicate and overlapping range detection with warnings
   Optional expiry / temporary rule support
   Encouraged or required reason/label field
4. Bulk Actions
   Bulk add, remove, or expire IPs
   Import/export support (CSV)
   Ability to move IPs between whitelist and blacklist
5. Operational Safety & Visibility
   Confirmation dialogs for high-impact actions (e.g. bulk deletes, wide CIDR changes)
   Per-entry audit history (who/when/what changed)
   Recent activity or “last blocked IPs” view with one-click whitelist
6. Permissions & Security
   Role-based access (read-only vs admin)
   Optional re-authentication for critical changes
7. Backend Consistency
   Web UI should use the same backend logic as the CLI to ensure consistent behavior
   Single source of truth for IP rule management
   Benefits
   Faster and safer IP management for administrators
   Improved visibility and auditability of IP rules
   Reduced reliance on CLI for routine tasks
   Better usability for less technical users without sacrificing power

Screenshots

For your consideration

[Aetherinox]

Good things on this list to definitely improve it.

I've got some other stuff currently that were put in before this, but once I get the higher priority items out, I'll put a plan together to start implementing some of these at a time.

[windsofchange]

Since the version number is not updated, will the auto updates pull these changes?

[Aetherinox]

What do you mean.

When I do the changes in this ticket, I'll roll out a release and bump the version number to whatever version comes next. Then once the version number updates, you'll be able to update on your end.

CSF doesn't do automatic updates. We let the users decide when they want to update. So if you're using the web interface, you'll get a little notification at the top saying an update is available.

Or you can run the terminal command sudo csf -c to check for updates. It'll tell you at that time if a new version is available, or if you're on the latest.

If it says there's a new version available; then you'll do the actual update with sudo csf -u

We don't push changes to a user right when they're made on the repo. That would set us up for disaster, especially if something is wrong in the code.

But the changes for this particular ticket have not been implemented yet. I'm doing bug fixes and minor tweaks at the moment. When I start working on a ticket, the progress will change to In Progress