Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Support wfpeter

    (@wfpeter)

    Hi @e5223959880, thanks for your message about this.

    We don’t think it’s necessary to try to prevent this reported issue. On most sites, an attacker can waste resources just as easily with regular pageloads if the responses are not cached outside of WordPress. An attacker in this case could request the same file multiple times in a single hit, which may increase resource usage but this was fixed in WordPress 4.9.5.

    Rapid7 list the solution as upgrading to WP 4.9.5, so if you’re up-to-date (or at least on or above that version) you shouldn’t need to take further action:
    https://www.rapid7.com/db/vulnerabilities/wordpress-cve-2018-6389/

    Thanks,
    Peter.

    Thread Starter A1234578

    (@e5223959880)

    Noted, thank you.

Viewing 2 replies - 1 through 2 (of 2 total)

The topic ‘Wordfence against CVE-2018-6389’ is closed to new replies.