• Resolved paulmersel

    (@paulmersel)


    Hi,

    After installing BPS I got a stream of helpdesk tickets about users not being able to get past the serial key validation screen. I immediately knew BPS had to be the problem and switching RBM off fixed the issue.

    Looking at my log I saw this:

    [403 GET Request: 11/04/2017 – 4:57 PM]
    BPS: 1.1
    WP: 4.7.3
    Event Code: BFHS – Blocked/Forbidden Hacker or Spammer
    Solution: N/A – Hacker/Spammer Blocked/Forbidden
    REMOTE_ADDR: 83.86.XXX.XXX
    Host Name: 5356EEBE.cm-6-7d.dynamic.ziggo.nl
    SERVER_PROTOCOL: HTTP/1.0
    HTTP_CLIENT_IP:
    HTTP_FORWARDED:
    HTTP_X_FORWARDED_FOR: 83.86.XXX.XXX
    HTTP_X_CLUSTER_CLIENT_IP:
    REQUEST_METHOD: GET
    HTTP_REFERER:
    REQUEST_URI: /?wc-api=validate_serial_key&serial=XXXXX&sku=XXXX&uuid=https://www.XXXXX.nl/
    QUERY_STRING:
    HTTP_USER_AGENT: NSIS_Inetc (Mozilla)

    So BPS is indeed blocking something. I tried to whitelist this URL in the # CUSTOM CODE BOTTOM HOTLINKING/FORBID COMMENT SPAMMERS/BLOCK BOTS/BLOCK IP/REDIRECT CODE without success. That is mainly because I am close to a NOOB in this level of coding.

    I did see that most whitelisting examples have a .php address which I haven’t..
    For example: RewriteCond %{REQUEST_URI} !^.*/wp-comments-post.php [NC]

    I (don’t laugh) tried : RewriteCond %{REQUEST_URI} !^.*/?wc-api=validate_serial_key [NC] which did not help.

    The question is how I can whitelist the above JSON POST/GET request?

    Any help would be very much appreciated.
    Paul

Viewing 15 replies - 1 through 15 (of 15 total)
  • Plugin Author AITpro

    (@aitpro)

    See the “POST Attack Protection Bonus Custom Code and WooCommerce store used on a website home page” help section in this forum topic: https://forum.ait-pro.com/forums/topic/woocommerce-read-me-first/ for how to add additional whitelist rules for WooCommerce (and other WooCommerce plugins) to the BPS POST Attack Protection Bonus Custom Code.

    • This reply was modified 7 years, 7 months ago by AITpro.
    Plugin Author AITpro

    (@aitpro)

    Oops this is a GET Request and not a POST Request. The top section of this forum topic: https://forum.ait-pro.com/forums/topic/woocommerce-read-me-first/ has whitelist rules that should whitelist the wc-api Query String, but you may need to add an additional Query String whitelist rule for the WooCommerce Serial Key plugin. See example below.

    Example:

    # WooCommerce shop, cart, checkout & wishlist URI skip/bypass rule
    RewriteCond %{REQUEST_URI} ^.*/(shop|cart|checkout|wishlist).* [NC]
    RewriteRule . - [S=14]
    
    # WooCommerce order & wc-ajax=get_refreshed_fragments Query String skip/bypass rule
    RewriteCond %{QUERY_STRING} .*(order|wc-ajax=get_refreshed_fragments|wc-api=validate_serial_key).* [NC]
    RewriteRule . - [S=13]
    • This reply was modified 7 years, 7 months ago by AITpro.
    • This reply was modified 7 years, 7 months ago by AITpro.
    Thread Starter paulmersel

    (@paulmersel)

    Hi AITpro,

    Thank you very much for your swift reply.

    I had already added the Woocommerce whitelist rules. Top one is the same, bottom one I replaced with your version. Unfortunately the problem persists.

    To be clear; I now have nothing in the CUSTOM CODE BOTTOM HOTLINKING/FORBID COMMENT SPAMMERS/BLOCK BOTS/BLOCK IP/REDIRECT CODE, only in the # PLUGINS/THEMES AND VARIOUS EXPLOIT FILTER SKIP RULES.

    Any suggestions? Do you need more info?

    Plugin Author AITpro

    (@aitpro)

    Did you do all of the Custom Code steps? Edit/change the custom code, Save it and then Activate Root Folder BulletProof Mode again.

    • This reply was modified 7 years, 7 months ago by AITpro.
    • This reply was modified 7 years, 7 months ago by AITpro.
    Thread Starter paulmersel

    (@paulmersel)

    Yes, I did (3 times)

    Plugin Author AITpro

    (@aitpro)

    Are you using any additional BPS Bonus Custom Code?

    Plugin Author AITpro

    (@aitpro)

    Hmm maybe the Query String is being seen as an RFI hacking attempt. I will test the Query String and see if that is what is being blocked: /?wc-api=validate_serial_key&serial=XXXXX&sku=XXXX&uuid=https://www.hacker-website.com/

    Thread Starter paulmersel

    (@paulmersel)

    No other custom code. Do you need the whole string without X’s?

    Plugin Author AITpro

    (@aitpro)

    I already tested the Query String and created a working solution and yep the Query String simulates an RFI hacking attempt against your website. I will create a forum topic for the WooCommerce Serial Key plugin on our forum site and post the link here with the working solution.

    Plugin Author AITpro

    (@aitpro)

    Thread Starter paulmersel

    (@paulmersel)

    WOW!

    This totally fixed it. Hope this helps others too.

    Thank you for your EXCELLENT support!

    Paul

    Plugin Author AITpro

    (@aitpro)

    Great! Thanks for confirming that worked.

    Plugin Author AITpro

    (@aitpro)

    We are adding a new Setup Wizard AutoFix feature to our BPS Setup Wizard that will automatically create whitelist rules for known issues with other plugins. The WooCommerce Serial Key plugin is a premium plugin so we cannot find the path for this plugin’s initialization file. Please go to the BPS System Info page > click the Get Plugins List button > copy the info that you see in the Plugins List for the WooCommerce Serial Key plugin and paste that info in your Reply. Example: WooCommerce Serial Key version # – Activated: example-path-to-plugin-initialization-file/example-file.php

    Thank you

    • This reply was modified 7 years, 6 months ago by AITpro.
    Thread Starter paulmersel

    (@paulmersel)

    Hi,

    here is the requested path:

    WooCommerce Serial Key 1.7.9 – Activated: woocommerce-serial-key/serial-key.php

    Hope this helps.
    Paul

    Plugin Author AITpro

    (@aitpro)

    Awesome! Very much appreciated paul. ??

Viewing 15 replies - 1 through 15 (of 15 total)
  • The topic ‘BPS RBM blocks woocommerce serial key plugin from validating serial key’ is closed to new replies.