As the world’s most popular content management system (CMS) today, WordPress is also one of the favorite targets of many hackers. Most websites receive continuous network attacks from numerous countries every day (mostly ineffective automated program scanning attacks).
In a common security protection understanding, one of WordPress’s system files, “XMLRPC.PHP”, is a very large vulnerability. The “Remote Procedure Call (RPC)” service it represents allows WP to exchange data with external servers, and because it is a necessary door that must be opened, it is treated as a primary target when hackers attempt attacks—a pitiable scapegoat that cannot escape blame (in fact, older versions of WordPress once had a serious vulnerability in this service that caused website attack incidents worldwide).
Restricting the XML-RPC Service with a Firewall
If the XML-RPC service could be forcibly shut down through a firewall, it would not cause too much trouble for website operation. Unfortunately, this service is a very important external liaison and referral station.
For example, the official JetPack plugin (including but not limited to) used by many site owners references it extensively. Therefore, once this service is blocked, the JetPack server will be unable to exchange data with our website, causing many convenient plugin features to become unusable and also affecting system stability.
Unless you do not need to block external attacks, or you have other security management mechanisms (such as installing the Wordfence security protection plugin or system-level host tools like Fail2ban and ModSecurity), you can write the fixed network channel addresses (IP addresses) between Jetpack and WordPress into the server configuration, opening the necessary channel for this service to keep it normally open. This strengthens server security while maintaining normal website operation.
Below are the currently known network addresses used by JetPack. We simply need to write them into the corresponding firewall whitelist table on the server, forcibly allowing the servers at the other end of these network addresses to connect normally with our server.
JetPack IPs Firewall Whitelist Network Addresses
- 122.248.245.244/32
- 54.217.201.243/32
- 54.232.116.4/32
- 192.0.80.0/20
- 192.0.96.0/20
- 192.0.112.0/20
- 195.234.108.0/22
References
- Hosting FAQ
Support Independent Perspectives & In-Depth Insights
Every thoughtful analysis and candid critique comes from our dedication to truth and quality. We choose not to follow sensational algorithms or clickbait headlines.
Sustaining independent research requires reader support. Make a one-time or monthly contribution, securely processed by Google.
Payments secured by Google · Manage or cancel anytime in your Google Account
Comments