• Resolved kalkat

    (@kalkat)


    Hi.
    I’m currently testing my website.
    I’m trying out typical behaviors of potential users.
    When I create an account, I get blocked by the WAF, as shown below.
    What am I doing wrong?

    Threat Score History for 146.70.37.180

    14.11.2026, 23:08:08waf+100Rule: (?i)(?:\.\.\/|\.\.\\|[\/\\\\](?:etc|windows|winnt|bin|boot|var|opt)[\/\\\\]|(?:\b(?:cmd\.exe|powershell\.exe|bash|curl|wget)\b|(?:/bin/sh|/usr/bin/sh|(?:\||;)\s*sh(?:\s|;|$))))
    <small>URI: /wp-json/spc/v1/optimizations</small>14.11.2026, 23:08:06waf+100Rule: (?i)(?:\.\.\/|\.\.\\|[\/\\\\](?:etc|windows|winnt|bin|boot|var|opt)[\/\\\\]|(?:\b(?:cmd\.exe|powershell\.exe|bash|curl|wget)\b|(?:/bin/sh|/usr/bin/sh|(?:\||;)\s*sh(?:\s|;|$))))
    <small>URI: /wp-json/spc/v1/optimizations</small>14.11.2026, 23:08:02waf+100Rule: (?i)(?:\.\.\/|\.\.\\|[\/\\\\](?:etc|windows|winnt|bin|boot|var|opt)[\/\\\\]|(?:\b(?:cmd\.exe|powershell\.exe|bash|curl|wget)\b|(?:/bin/sh|/usr/bin/sh|(?:\||;)\s*sh(?:\s|;|$))))
    <small>URI: /wp-json/spc/v1/optimizations</small>14.11.2026, 23:08:00waf+100Rule: (?i)(?:\.\.\/|\.\.\\|[\/\\\\](?:etc|windows|winnt|bin|boot|var|opt)[\/\\\\]|(?:\b(?:cmd\.exe|powershell\.exe|bash|curl|wget)\b|(?:/bin/sh|/usr/bin/sh|(?:\||;)\s*sh(?:\s|;|$))))
    <small>URI: /wp-json/spc/v1/optimizations</small>14.11.2026, 23:07:24403+10URI: /wp-json/faz/v1/banner/en?banner=gdpr-1

    The page I need help with: [log in to see the link]

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author IniLerm

    (@inilerm)

    Hi @kalkat,

    You are not doing anything wrong! What you are seeing is a false positive triggered by a legitimate REST API endpoint used by Super Page Cache (/wp-json/spc/v1/optimizations), whose request payload/parameters matched our WAF’s system-path / path-traversal protection rule.

    Because regular visitors and new users registering on your site also trigger this endpoint, whitelisting only your admin IP wouldn’t fix it for them. Here is how to resolve it cleanly for all visitors:

    1.Exclude the endpoint from the WAF

    1. Go to Security → Settings → Web Application Firewall (WAF).
    2. Find the Excluded URLs for WAF field.
    3. Add the following line:
      /wp-json/spc/v1/
      (or specifically /wp-json/spc/v1/optimizations)
    4. Save changes.

    (Optional: If you also want to prevent background REST calls from counting toward 403/404 error thresholds, you can add /wp-json/spc/v1/ to Global URL Exclusions under Security → Settings → General Settings as well.)

    2. Unblock your test IP (146.70.37.180)

    • Go to Blocked IPs (or Threat Scoring) in the plugin and unblock/reset 146.70.37.180 so you can continue testing immediately.
    • Tip for your own admin access: When working as an administrator (especially if you use a dynamic IP or VPN), make sure your IP is in the Whitelist or enable Auto-Whitelist Admins under Security → Settings → Login & User Protection so you never lock yourself out while configuring the site.

    Let us know if the registration test works smoothly after adding that WAF exclusion!

    • This reply was modified 6 days, 6 hours ago by IniLerm.
    • This reply was modified 6 days, 6 hours ago by IniLerm.
    Plugin Author IniLerm

    (@inilerm)

    Quick update for @kalkat and anyone else following this thread:

    Thank you again for sharing the exact WAF log entry—reports like yours are incredibly helpful.

    Based on your report, we have just refined that path/command inspection rule on our Central Zero-Day WAF feed so it no longer triggers false positives on legitimate REST API endpoints and JSON payloads (like Super Page Cache’s /wp-json/spc/v1/optimizations) while keeping full protection against real Path Traversal and RCE attempts. Your site will receive the updated rule automatically on its next scheduled WAF sync.

    A Helpful Tip for All Users

    • Immediate local fix: Whenever you encounter a WAF false positive on a legitimate plugin or theme endpoint, you can resolve it right away by adding the affected URI path (e.g., /wp-json/spc/v1/) to Excluded URLs for WAF under Security → Settings → Web Application Firewall (WAF).
    • Help improve the firewall for everyone: Please continue reporting any false positives here in the support forum with the anonymized Threat Score / WAF log details. When you share them with us, we can investigate the exact pattern, fine-tune our Zero-Day WAF rules centrally, and push improvements that benefit the entire Advanced IP Blocker community.

    Thanks again for the feedback!

    Thread Starter kalkat

    (@kalkat)

    I applied your solution, and it works very well.
    Thank you very much, and best regards.

    Best regards,

    PS I have been blocked from the website https://advaipbl.com/. I’m not sure why.
    “The owner of this website (advaipbl.com) has banned your IP address (xx.xx.120.10).”

    Plugin Author IniLerm

    (@inilerm)

    Hi @kalkat,

    First and foremost, a huge thank you for your generous donation! We truly appreciate your support—it means a lot to us and motivates us to keep actively improving Advanced IP Blocker.

    The Zero-Day Rule Update (Resolved)

    Regarding the false positive you reported:
    We analyzed the rule and immediately updated the regex pattern. The check on /opt was indeed matching legitimate subpaths like /wp-json/spc/v1/optimizations. We have already updated our central rule feed, so your installation will automatically pull the clean rule during its normal update cycle.

    Tip for the future: If you ever encounter a false positive on a custom REST API endpoint, you can temporarily exclude it in Security -> Settings -> Web Application Firewall (WAF) -> Excluded URLs for WAF. Reporting it here as you did helps us refine the signatures for all users!

    Note on Your IP Block on Our Website (Fixed & Unblocked)

    While reviewing our server logs to confirm your donation, we noticed that your IP (8x.x3.120.10) had been temporarily blocked on our website (advaipbl.com).

    We investigated why this happened and discovered another false positive: when you clicked to visit our website from your WordPress dashboard, your browser passed the referrer header:
    .../wp-admin/plugin-install.php

    Our central WAF’s installer-protection rule flagged plugin-install.php due to a regex boundary matching install.php. We have unblocked your IP immediately and fixed that rule on our servers as well.

    Thank you so much once again for your feedback, patience, and kind support!

    Best regards,
    The Support Team

    • This reply was modified 5 days, 14 hours ago by IniLerm.
    • This reply was modified 5 days, 14 hours ago by IniLerm.
    • This reply was modified 5 days, 14 hours ago by IniLerm.
Viewing 4 replies - 1 through 4 (of 4 total)

You must be logged in to reply to this topic.