China Web Guide

WordPress Security in China: Updates and Crawlers

Why a mainland WordPress install falls behind on patches, and how its own WAF can lock Baidu out.

In a Nanjing agency office, a developer in a dark hoodie points a pen at the WordPress Updates screen in Chinese on her laptop, while a colleague holding a cup of tea looks at an Alibaba Cloud WAF crawler allowlist on the monitor behind.

WordPress security in China fails in two quiet ways. On a server in the mainland, WordPress.org’s update servers answer with HTTP 429, so core and plugin updates stop and the dashboard says nothing about it. Then the security plugin added to make up for the gap can turn away the Chinese search crawlers the site was built for.

Neither failure shows up there. You can check both on your own install today.

ProblemWhere it startsWhat you seeFirst fix
Updates stopWordPress.org rate limits Chinese network sourcesNothing: no update notice, no automatic security releaseA mirror, a proxy, or updates run from outside the mainland
The plugin’s own rules arrive lateWordfence free gets new firewall rules 30 days after PremiumA clean scan resultPatching that works, with the plugin as a second layer
Crawlers get refusedA crawler rate limit, a ban list or a country ruleIndex counts on Baidu, 360 or Shenma that stop movingVerify the crawler by reverse DNS before any rule counts it

The update servers answer, then refuse

The WordPress.org sites connect from mainland China. GreatFire, which tests reachability from inside the Great Firewall, reads both as reachable.

GreatFire reads https://wordpress.org as reachable from mainland China, with all 13 recent conclusive tests connecting normally and the latest test on 1 November 2026. http://api.wordpress.org connected on its one recent conclusive test, on 7 October 2026. Source: GreatFire, read 3 November 2026. https://en.greatfire.org/https/wordpress.org and https://en.greatfire.org/http/api.wordpress.org

The refusal comes from WordPress.org itself.

WordPress.org told a user in China who was getting HTTP 429 errors that several Chinese network sources are rate limited “due to a high level of abuse and non-legitimate traffic”, and that it would not offer whitelisting or an official way to replicate WordPress.org through a Chinese proxy. Source: WordPress.org Meta Trac, ticket #5106, 21 March 2020. https://web.archive.org/web/20260116133057/https://meta.trac.wordpress.org/ticket/5106

What happens next is written in WordPress’s own code. The core version check posts to api.wordpress.org, and any reply other than HTTP 200 ends the function on the spot. The hook that starts automatic background updates sits further down. It never fires.

In WordPress 7.1.3, wp_version_check() returns as soon as the reply is an error or anything other than HTTP 200. The wp_maybe_auto_update hook, which starts background updates, fires only after a good reply. Automatic minor core updates are on by default. Source: WordPress core 7.1.3, wp-includes/update.php and wp-admin/includes/class-core-upgrader.php, read 3 November 2026. https://raw.githubusercontent.com/WordPress/WordPress/7.1.3/wp-includes/update.php

So the safety net WordPress ships for security releases does nothing on a server that gets a 429. Plugins and themes from the WordPress.org directory check the same API, so they stall together. No email goes out and no notice appears. The site stays on whatever versions it had the day the limit started biting.

The Updates screen makes it harder to spot. WordPress stamps the time of a check before it sends the request, so a check that failed still shows up as fresh.

WordPress 7.1.3 sets last_checked to the current time before the request to api.wordpress.org goes out, “to prevent multiple blocking requests if request hangs”. Dashboard > Updates prints that value as “Last checked on”. Source: WordPress core 7.1.3, wp-includes/update.php and wp-admin/update-core.php, read 3 November 2026. https://raw.githubusercontent.com/WordPress/WordPress/7.1.3/wp-admin/update-core.php

A screen that reads “Last checked on” this morning, with nothing to update, proves nothing on a mainland server. Compare the version numbers on the Plugins screen with the plugin pages on WordPress.org, from a browser outside the server. If they differ and WordPress offers nothing, the checks are failing.

The same 429 is also why the admin drags, which our guide to why wp-admin is slow in China covers. This guide is about the patches.

Why WordPress security in China comes down to patching

Nine in ten new WordPress vulnerabilities are in plugins, and the worst of them are attacked within hours of being published.

Patchstack counted 11,334 new vulnerabilities in the WordPress ecosystem in 2025, 42% more than in 2024. 91% were in plugins and 9% in themes; WordPress core had 6. About half of high-impact vulnerabilities were exploited within 24 hours of disclosure. Source: Patchstack, State of WordPress Security in 2026, February 2026. https://patchstack.com/whitepaper/state-of-wordpress-security-in-2026/

Hours, set against a site that has stopped asking for updates at all.

A fast patch doesn’t close every gap either.

46% of the vulnerabilities in Patchstack’s 2025 data did not receive a fix from the developer in time for public disclosure. Source: Patchstack, State of WordPress Security in 2026, February 2026. https://patchstack.com/whitepaper/state-of-wordpress-security-in-2026/

Even a team that updates the day a fix ships has a window of exposure. On a mainland server with no working updates, that window stays open until a person notices, and the dashboard gives them no reason to look.

Four ways to keep a mainland site patched

RouteHow it worksWhat it costs youWatch for
A mirror pluginWP-China-Yes, now WPCY.COM (3.9.3, tested to WordPress 7.1), sends WordPress.org calls to mainland mirrors and falls back to the original when a mirror failsThird-party code between your site and its updatesIt was closed in the WordPress.org directory in April 2020 and lives on GitHub. Read it before you install it
A proxy in wp-config.phpWP_PROXY_HOST and WP_PROXY_PORT send WordPress’s outbound requests through a proxy you run outside the rate-limited rangesA second server and its upkeepUse WP_PROXY_BYPASS_HOSTS so local and mainland services skip the proxy
Updates from outsideUpdate a staging copy on a server elsewhere, test it, deploy the files to the mainland serverA deploy pipeline and someone to run itSet DISALLOW_FILE_MODS on the live site so the dashboard can’t half-update it
A maintenance retainerSomeone owns the schedule and checks versions against the advisoriesA contract with an outside teamAsk how their updates get past the 429

WordPress core 7.1.3 reads WP_PROXY_HOST, WP_PROXY_PORT, WP_PROXY_USERNAME, WP_PROXY_PASSWORD and WP_PROXY_BYPASS_HOSTS from wp-config.php. DISALLOW_FILE_MODS switches off file changes from the admin, updates and installs included. Source: WordPress core 7.1.3, wp-includes/class-wp-http-proxy.php and wp-includes/load.php, read 3 November 2026. https://raw.githubusercontent.com/WordPress/WordPress/7.1.3/wp-includes/class-wp-http-proxy.php

The mirror is the quickest to set up and the hardest to audit. On the sites we run, we use the proxy or scheduled update windows, as our WordPress in China page explains.

Whichever route you pick, somebody still has to compare version numbers with the advisories every week, because WordPress won’t prompt them. In practice that means reading the week’s disclosures for every plugin on the site, updating a staging copy first, then the live server, and keeping a dated note of what changed. That weekly routine sits at the centre of our Maintenance and Support service.

The security plugin can’t stand in for patches

The usual response to a site that can’t update is a security plugin. It helps less than people expect on a mainland server, for two reasons.

The first is timing.

The free version of Wordfence gets new firewall rules and malware signatures from the Threat Defense Feed 30 days after Premium customers. Source: Wordfence 9.0.2 readme, WordPress.org, updated 30 September 2026. https://wordpress.org/plugins/wordfence/

Thirty days, against a first exploit that Patchstack measures in hours. The feed also comes from Wordfence’s own servers, and GreatFire has never tested noc1.wordfence.com, the plugin’s main API host. Its behaviour from the mainland is untested, so we give it no verdict. And the plugin’s own updates come from WordPress.org, behind the same 429.

The second reason is collateral damage. Two settings in two popular plugins can refuse Chinese search crawlers, and neither logs it where you would look.

Wordfence 9.0.2 ships its five rate limits disabled, and its only crawler setting exempts verified Google crawlers. Solid Security 10.0.6 ships “Default Ban List” off; switched on, it writes a 403 for user agents containing 360Spider, YisouSpider and EasouSpider into the server configuration. Source: Wordfence and Solid Security source code, WordPress.org, read 9 and 29 October 2026. https://wordpress.org/plugins/wordfence/ and https://wordpress.org/plugins/better-wp-security/

Type a number into Wordfence’s “If a crawler’s page views exceed” and Googlebot walks past it while Baiduspider is counted like any other bot. Past the limit it gets a 503. Solid Security’s list, now shipped under the Kadence Security name, shuts out 360 Search (360搜索) and Shenma Search (神马搜索) at the server, before WordPress sees the request. Baiduspider isn’t on it.

Our guide to Baiduspider blocked by Cloudflare and WAF rules goes through both settings line by line. It also clears the two cache plugins people suspect first: LiteSpeed Cache and W3 Total Cache ship their user agent lists empty and have no rule that names Baiduspider.

Check the crawler before a rule counts it

A user agent is a header anyone can type. Baidu’s documented check is a reverse lookup.

A genuine Baiduspider address resolves to a hostname ending in .baidu.com or .baidu.jp, and a forward lookup of that hostname must return the original address. Baidu says its crawler’s IP ranges change and it cannot publish them. Source: Baidu Search Resource Platform (百度搜索资源平台), February 2022. https://ziyuan.baidu.com/college/articleinfo?id=3378

That rules out an IP allowlist built from a blog post, which is all Wordfence’s allowlist accepts. So rate limit crawlers at the edge, where a rule can run the lookup first, or keep crawler limits off in the plugin.

A mainland cloud gives you one more option. Alibaba Cloud’s (阿里云) WAF ships a Baidu allowlist that you switch on per domain.

Alibaba Cloud’s Web Application Firewall has allowed-crawler rules that include a Baidu spider allowlist (百度蜘蛛白名单), alongside Google, Sogou, Bing and Yandex. They need the Bot management module. Once a rule is on, those crawler addresses skip Bot management checks; access control and rate limit rules can still filter them. Source: Alibaba Cloud (阿里云), Web Application Firewall 2.0 documentation, 设置合法爬虫规则, updated 17 September 2026. https://help.aliyun.com/zh/waf/web-application-firewall-2-0/user-guide/configure-the-allowed-crawlers-function

Country blocks catch Baidu’s crawler too

The bluntest rule is a country block on China, often added in the middle of an attack and never taken off. Baidu crawls from mainland networks, so that rule catches it too.

111.206.198.69, the crawler address in Baidu’s own worked example, sits in 111.192.0.0 to 111.207.255.255, a block APNIC lists as China Unicom (中国联通) Beijing province network, country CN. Source: APNIC RDAP record, last changed 21 October 2023, read 3 November 2026. https://rdap.apnic.net/ip/111.206.198.69

If the block stays, scope it to wp-login.php and wp-admin and leave the public pages open. On the login page itself, two-factor login and a rate limit on wp-login.php do more than a country rule, and neither touches a crawler.

Cloudflare’s in-country option is a different product with its own paperwork.

Cloudflare China Network is a separate subscription for Enterprise customers, run in mainland data centres by JD Cloud. Each apex domain needs an ICP filing or licence and JD Cloud’s content review. Source: Cloudflare, China Network overview and Get started documentation, April 2026. https://developers.cloudflare.com/china-network/ and https://developers.cloudflare.com/china-network/get-started/

On the global network, there’s no promise of a nearby edge.

Cloudflare says the visitor’s ISP decides which Cloudflare data centre receives a request, based on its own routing and peering policies, and that these do not always favour the geographically closest location. Source: Cloudflare, geographic traffic routing documentation, October 2026. https://developers.cloudflare.com/support/troubleshooting/general-troubleshooting/geographic-traffic-routing/

Our guide to Cloudflare in China covers the filing requirement and what changes for mainland visitors.

Frequently asked

Does Wordfence work on a server in mainland China?

The plugin runs, and its firewall works on the rules it already has. Its own updates come from WordPress.org, though, so the 429 can hold them back, and the free feed runs 30 days behind Premium. GreatFire has never tested its API host, noc1.wordfence.com. Keep its crawler rate limits off unless you set them well above what a crawl sends.

Is WP-China-Yes safe to install?

It’s open source and still maintained as WPCY.COM, at version 3.9.3, tested to WordPress 7.1. WordPress.org closed it in its directory in April 2020 for a guideline violation. It sits between your site and every update, so read the code, pin the version, and check where its mirrors point before you trust it with patches.

Will automatic updates work if I host in China?

Only when the version check gets an HTTP 200 back. WordPress starts background updates after a good reply from api.wordpress.org, and a 429 stops the process silently. On a mainland server, plan on a mirror, a proxy or updates run from outside, then compare your version numbers with WordPress.org each week.

Should I block China in Cloudflare to stop attacks?

Keep any country rule to wp-login.php and wp-admin if you want Chinese search traffic. Baidu’s crawler works from mainland address blocks, so a site-wide rule refuses it along with the attackers. For anything stricter on the public pages, verify crawlers by reverse DNS first and let the rule skip the ones that pass.

Need help with this?

ChinaWebFoundry handles WordPress projects in China end to end. If any of this feels like more than you want to tackle alone, get in touch.

Talk to Us