Practical WordPress advice for website owners

WordPress Still Gets Attacked Behind Cloudflare? Check Direct Access to the Origin Server

Editorial portrait illustration for: WordPress Still Gets Attacked Behind Cloudflare? Check Direct Access to the Origin Server
Editorial illustration using Nithu’s supplied portrait; not a client incident screenshot or measured result.
In this guide

A WordPress site can still receive unwanted requests behind Cloudflare if the origin server accepts traffic that bypasses the proxy. Ask the host to verify the actual route and origin access controls. Cloudflare DNS proxying does not, by itself, prove that direct connections to the web server are rejected.

Start with evidence. Requests reaching WordPress may have passed Cloudflare normally, arrived through a DNS-only hostname or reached an exposed origin directly. The existence of attacks in a security log is not enough to distinguish those paths or prove that Cloudflare protection failed.

Map every route to the web server

Inventory the public domain, www, shop and API hostnames, staging names, old migration destinations and any host-provided preview domain. Record which web records are proxied, which are DNS-only and which destination addresses they use. Include IPv6 where configured.

Keep web and non-web services distinct. Mail and other services may legitimately use DNS-only records and require different network access. Do not proxy every record or block every port as a quick response to a WordPress security concern.

Ask the host to establish:

  • Which public addresses and virtual hosts can serve the WordPress installation.
  • Whether an authorized direct-origin request can reach the site with its intended hostname.
  • Which network and web-server controls already restrict access.
  • Whether logs reliably distinguish Cloudflare connections from other connections.
  • Which legitimate services currently use direct origin access.

Arrange these checks only for infrastructure you own or are authorized to assess. The administrator should preserve normal hostname and TLS behavior during the comparison; simply entering an IP address into a browser can select a different virtual host and yield an inconclusive result.

Understand what each control proves

Cloudflare’s origin-protection guidance describes several approaches, including network restrictions, Authenticated Origin Pulls and Cloudflare Tunnel. The best supported choice depends on the host, architecture and legitimate dependencies. A shared-hosting customer may need the provider to implement controls rather than editing a server firewall personally.

Network restrictions can limit web access to approved Cloudflare ranges and any specifically justified sources. They require maintained address lists and attention to all serving addresses. Tunnel can change the public exposure model, but it is a deployment choice requiring compatible host access and operational support.

Do not confuse the certificate the origin presents to Cloudflare with authentication of the client connecting to the origin. Full (strict) validates the origin’s server certificate. Authenticated Origin Pulls adds client-certificate authentication in the other direction.

Cloudflare’s AOP explanation warns that its global certificate is shared and proves traffic comes from the Cloudflare network, not specifically your account. Stricter isolation can require zone-level or hostname-level AOP using your own certificate, plus other appropriate controls. Select a method that matches the security requirement rather than describing the shared certificate as account-exclusive.

List dependencies before tightening access

The owner can identify external services and responsible contacts. The developer should trace integrations and hosting routes. The host or network administrator should implement and validate the supported server controls.

Review uptime monitoring, backup agents, deployment tools, payment callbacks, remote publishing, certificate renewal and administrative access. Determine whether each can use the normal proxied hostname or needs a narrowly defined exception. A generic “allow all partners” rule undermines the purpose of the restriction.

Check emergency access too. Maintain an approved way for administrators to recover a failed deployment without opening the website to everyone. Document the dependency owner, required path and review date for any exception.

The DNS migration guide helps identify connected services. Keep this work focused on origin access; the broader Cloudflare WAF rollout guide addresses rules applied to proxied requests.

Apply the change in a controlled sequence

Preserve the current configuration and rollback method. Test on a representative nonproduction route or a controlled maintenance window where possible. Configure the origin to recognize and enforce the chosen authentication, then enable the corresponding Cloudflare behavior in the sequence supported by the vendor and host.

Turning a dashboard option on without origin enforcement is not sufficient evidence that direct requests are blocked. Conversely, requiring a client certificate before the intended proxy can supply it can make the site unavailable. The administrator should validate both ends and every active origin node.

Do not rotate the origin IP as the only protective measure. It may reduce some known direct traffic, but the acceptance test remains whether unauthorized access is rejected under the actual configuration. Any new address also needs consistent firewall, certificate and monitoring setup.

Verify rejection and legitimate operation

Have the host demonstrate that an authorized controlled direct test is rejected while normal proxied traffic works. Check all origin addresses and relevant hostnames, and verify that restrictions cover the intended web ports. Do not rely solely on an absence of recent malicious traffic.

Then test public pages, administration, forms, scheduled integrations, certificate renewal arrangements and supported payment callbacks. Confirm a test transaction or enquiry produces the expected application record. Review monitoring and backup jobs after their next scheduled run.

If the new restrictions cause a connection timeout, use the Cloudflare 522 diagnosis to inspect reachability rather than immediately removing every origin control. Record the final access model, exceptions and responsible maintainer so a later migration does not silently undo the protection.

FAQs

Does hiding my origin IP guarantee protection?

No. Base the protection on enforced access controls and authentication. An address becoming known should not automatically allow an unauthorized request to reach WordPress.

Is a Cloudflare Origin CA certificate the same as AOP?

No. The origin’s server certificate and the client authentication used by Authenticated Origin Pulls serve different roles. Ask the host to document which directions are validated.

Does the global AOP certificate identify only my Cloudflare account?

No. Cloudflare states that the shared global certificate authenticates its network. More specific authentication requires an appropriately configured customer certificate or other supported controls.

Prepared for website owners by Nithu / Suthakaran Nithursan. Dated advisory facts link to primary sources. Examples are illustrative and are not client results or guarantees.