solventweb

Thanks @wfpeter. That’s good advice. FYI the pages in question aren’t 404s.

My main hesitation with the robots.txt change is that not all crawlers will respect it (especially those operating in grey areas). I’d prefer to enforce a rate limit on our end. Do you have any advice on how this might be accomplished with your plugin? For example, could we customize your WAF’s auto_prepend_file to include your rate limiting functions?

Hi @faisalahammad. Thanks for your reply. You can replicate the issue by:

1. Install Ninja Forms on a fresh WP install.
2. Add the default form to any page.
3. Run a WAVE accessibility scan on the page.

If do these steps, you’ll see errors like the ones indicated in this screenshot.

Thanks @wfscott. I’ll reach out at the email address you suggested.

Hi @wfscott ,

Thanks for your response! I understand that IPs change frequently so I’m not looking for a permanent block. However, if an IP address makes several malicious requests within a short period, I would like to automatically apply a temporary block (similar to your brute force protection).

Frankly, I’m surprised to learn your plugin doesn’t work that way by default. Is there any way that your free plugin can be configured to accomplish that? Is this a feature of your premium plugin?

FYI in the case of this particular attack, the VPS was completely bogged down with malicious requests. Going forward, I’d prefer not have to manually block offending IPs just to keep a site available.

Again, any help or advice is appreciated!

Thanks for your help @wfmark

Thanks @wfmark. Here’s what I see:

Access: 2024-01-04 19:41:43.347199483 +0000
Modify: 2024-01-01 20:10:04.660077352 +0000
Change: 2024-01-04 19:43:25.219974912 +0000
Birth: 2024-01-01 20:10:04.660077352 +0000

So I assume that’s good?

Thanks for your response @wfmark. Because of the configuration of our site, the URL I mentioned will always return an error. So I’m wondering if there’s a different way to trigger an update to malware signatures and rules. Ideally, I’d like to do this with a cronjob. Let me know if that’s possible.

Thanks @joostvandevijver. I’ll post back here if I’m able to reproduce the error. Until then I’ll close the topic.

@pixelgrade, thanks for the response. Do you have an ETA on the release of the updated version?

Hi @wfpeter, just checking in. Any updates?

Thanks @wfpeter. Sent.

Hi @wfpeter, thanks for your response.

Under Wordfence > Login Security > Settings > General, I see the following: “NTP is currently disabled as 3 subsequent attempts have failed.”

Under Wordfence > Login Security, “Server Time” and “Browser Time” both appear to be correct. I don’t see “Corrected Time” though…

Server Time: 2023-07-12 22:50:32 UTC (2023-07-12 16:50:32 UTC-6)
Browser Time:?Wed, 12 Jul 2023 22:50:32 GMT (Wed Jul 12 2023 17:50:32 GMT-0500 (Central Daylight Time))

@constantcontact, Patchstack says the issue was reported by Lana Codes with “no reply from the vendor.” So apparently they were unable to contact you. I suggest you reach out to them directly:

• https://lana.codes/
• https://twitter.com/LanaCodes

Same issue here

Perfect. Thanks for your help.