Overview
Many common Content Management Systems (CMS) relay information with your website that can appear malicious through its automated nature. StackPath can identify CMS admin user traffic to prevent blocking needed traffic. Additionally, StackPath's library of known malicious attacks can block exploits that have attacked users in the past.
Most of the toggles in this area ALLOW traffic except for the first item which is meant to BLOCK traffic.
StackPath recommends leaving these toggles OFF if that particular CMS is not in use.
| Name | Description |
| Wordpress WAF Ruleset | Block requests that are potentially a WordPress exploit. |
| Logged-In WordPress admins | Allow requests from logged-in WordPress admins. |
| Logged-in MODX admins | Allow requests from logged-in MODX admins. |
| Logged-in Drupal admins | Allow requests from logged-in Drupal admins. |
| Logged-in Joomla admins | Allow requests from logged-in Joomla admins. |
| Logged-in Whitelist Magento admins | Allow requests from logged-in Magento admins. |
| Requests from Origin's IP | Allow requests from the origin's IP address for updates. |
| Logged-in Umbraco admins | Allow requests from logged-in Umbraco admin users. |
| Logged-in PimCore admins | Allow requests from logged-in PimCore admin users. |
Allowing Admin Users
In some cases, administrative sections of a CMS-based website may be blocked. For example, for WordPress, the WAF may label a change made to the /wp-admin section of a CMS-based site as malicious behavior, such as a Cross Site Scripting or SQL injection. As a result, the WAF will block you from making any page edits.
The section below will review the two options you can use to prevent such issues from occurring:
Option 1: Whitelist your static IP address
- In the StackPath Control Portal, in the left-side navigation menu, click Sites.
- Locate and select the desired site. This action will refresh the portal.
- In the left-side navigation menu, click Firewall.
- For Allowed IPs, click Add IP/IP Range.
- In the entry that appears, enter your public IP address so that all traffic from your IP will be allowed (whitelisted) and will not be blocked by the WAF for any type of request.
Option 2: Use the CMS Protection policies to enable logged-in admins
StackPath's WAF features specific rules that detect when a user is logged-in to a supported CMS and automatically whitelists the user's session.
- In the StackPath Control Portal, in the left-side navigation menu, click Sites.
- Locate and select the desired site. This action will refresh the portal.
- In the left-side navigation menu, click WAF.
- Under CMS Protection, locate your CMS for admin logged-in users, and then slide On.
- If you do not see your CMS, please contact Support. You may also use option 1 as a solution.
- With this action, when an admin user logs into the site, their CMS session will be whitelisted.
