Limited-Time Offer

Get Extra 20% off on FullCharge Yearly Plan — available for first 10 users only. Don’t miss out! 🚀

TrackWP

Cloudflare · Version history

Cloudflare changelog and version history

Latest version
4.14.5
Oct 5, 2026 (1 month ago)
Releases
94
since 2016
In the last year
6
about one every 58 days
Tested up to
WordPress 7.1.4
PHP 7.4 or later

Releases each year

  • 201636 releases
  • 20175 releases
  • 20193 releases
  • 202012 releases
  • 202113 releases
  • 20229 releases
  • 20233 releases
  • 20246 releases
  • 20254 releases
  • 20263 releases

20263 releases

  1. Cloudflare 4.14.5Latest

    • Fixed
    • Trashing a published post now purges the post’s public URL from the Cloudflare cache, also when a trashed post with the same slug already exists.
    • Failed connections to the Cloudflare API now show the reason instead of a generic “Request error”, without PHP warnings.
    • PHP 8.1+ deprecation notices when a request has empty or missing input.
    • Activating the plugin on an unsupported WordPress version now deactivates it again with a notice.
    • Changed
    • Requires WordPress 6.7 or newer, as the plugin now supports the five latest major WordPress versions.
    • Tested up to WordPress 7.1.2.
    • Improved the automated tests and CI, including tests on the five latest WordPress versions and compatibility tests with popular plugins.
    • Security
    • Compare CSRF tokens in constant time.
    • Escape output on the settings page and sanitize input to the settings page proxy.
    • Only use the CF-Connecting-IP header as the visitor IP address when it holds a valid IP address.

  2. Cloudflare 4.14.4

    • Fixed
    • Guard against non-string parse_url result in pathIsNotForFeeds.
    • Added
    • Unit tests for Hooks.php covering private helpers, purgeCacheByRelevantURLs, isEnabled methods, getPostRelatedLinks, and cache purge event handlers.
    • Extract WP core class stubs into a shared test fixture and bootstrap.
    • Changed
    • Bumped symfony/yaml from 5.4.45 to 5.4.52.
    • Bumped symfony/polyfill-intl-idn from 1.37.0 to 1.38.1.
    • Security
    • Declare least-privilege permissions on php-build, php, and stale CI workflows.

  3. Cloudflare 4.14.3

    • Fixed * FQCN references are now correctly rewritten by update-namespaces.php during build. * Fixed double pipes typo after ttf in htaccess. * Recognize new cfk_/cfut_/cfat_ credential formats * Apply settings fail-fast when using Account Owned Tokens * Partial-failure test silently overwriting mess…
    • Changed
    • Replace FQCN type hints with imported aliases for LoggerInterface.

20254 releases

  1. Cloudflare 4.14.2

    • Fixed
    • Set correct type for $logger parameter in deprecated CF\WordPress\Datastore constructor.
    • Changed
    • Removed contructor parameter types from deprecated CF\Integration\DefaultIntegration to prevent outdated integration errors.
    • Instead of directly loading the polyfil Normalizer in global namespace, patched polyfill-intl-idn to use vendor prefixed Normalizer.

  2. Cloudflare 4.14.1

    • Fixed
    • Fixed classmap autoloading for deprecated classes in release builds issue. Solving conflicts with plugins that directly use deprecated namespace.
    • Add IntlUtil helper class to fix symfony polyfill-intl loading; include Resources/unidata, load Normalizer stub via files autoload, and patch circular constant references.

  3. Cloudflare 4.14.0

    • Added
    • Add PHP-Scoper build system for vendor namespace prefixing.
    • Changed
    • Tested with WordPress 6.9 release and bumped “Tested up to” up to 6.9.0.
    • Deprecated
    • Namespace CF in favor of Cloudfare\APO, to resolve and prevent namespace conflicts with other plugins.

  4. Cloudflare 4.13.0

    • Changed
    • Bumping required PHP version to 7.4 and updating relevant code to support this change.
    • Upgraded symfony/yaml dependency to ^5.4
    • Update various meta information.

20246 releases

  1. Cloudflare 4.12.8

    • Prevent default settings from enabling Auto Minify due to deprecation (#547)

  2. Cloudflare 4.12.7

    • Upgrade cloudflare-plugin-frontend to v3.10.0 (#542)

  3. Cloudflare 4.12.6

    • Upgrade cloudflare-plugin-frontend to v3.9.0 (#537)

  4. Cloudflare 4.12.5

    • Upgrade cloudflare-plugin-frontend to v3.8.0 (#535)
    • Retrieve the WordPress domain only from the active zone (#532)

  5. Cloudflare 4.12.4

    • Fix “creation of dynamic property is deprecated” notice

  6. Cloudflare 4.12.3

    • Prevent usage of cloudflare_proxy action on /admin-ajax endpoint for non-Administrator users

20233 releases

  1. Cloudflare 4.12.2

    • Revert the incorrect fix to Cloudflare Partners endpoint

  2. Cloudflare 4.12.1

    • Fix Cloudflare Partners endpoint

  3. Cloudflare 4.12.0

    • Updated plugin to be tested on WordPress 6.2

20229 releases

  1. Cloudflare 4.11.0

    • Restrict access to sensitive files using .htaccess configuration.
    • Added cloudflare_use_cache hook to determine when to cache.
    • Allow arrays with url keys to be passed into cache purge requests.
    • Handle getZoneSettings not returning a key and throwing an unset array key error.

  2. Cloudflare 4.10.1

    • Fix logic for ignoring cache purge operations.

  3. Cloudflare 4.10.0

    • Ignore feed URLs in cache purge operations unless a cache override is in place.

  4. Cloudflare 4.9.1

    • Handle empty URL arrays for purging.
    • Swap publicly_queryable for is_post_type_viewable when determining if the post is public.
    • Update always_use_https check to work with the API lacking a “value” for the key.
    • purgeCacheByRelevantURLs now accepts either an array or single ID

  5. Cloudflare 4.9.0

  6. Cloudflare 4.8.3

    • When a zone has “Always Use HTTPS” enabled, only send HTTPS based URLs. HTTP URLs will never be hit and never present in the cache.

  7. Cloudflare 4.8.2

    • Retag 4.8.1 with correct version in user agent

  8. Cloudflare 4.8.1

    • Loosen domain check for cache purge calls to allow subdomains

  9. Cloudflare 4.8.0

    • Updated supported WordPress version to 5.9
    • Replace Guzzle with wp_remote_request for remote calls
    • Update cache purge logic to improve efficiency of what we send to the remote service

202113 releases

  1. Cloudflare 4.7.0

    • Merge cloudflare-plugin-backend into Cloudflare-WordPress repository

  2. Cloudflare 4.6.0

  3. Cloudflare 4.5.1

  4. Cloudflare 4.5.0

  5. Cloudflare 4.4.0

  6. Cloudflare 4.3.0

  7. Cloudflare 4.2.2

  8. Cloudflare 4.2.1

  9. Cloudflare 4.2.0

  10. Cloudflare 4.1.0

  11. Cloudflare 4.0.0

  12. Cloudflare 3.8.9

  13. Cloudflare 3.8.8

202012 releases

  1. Cloudflare 3.8.7

  2. Cloudflare 3.8.6

  3. Cloudflare 3.8.5

  4. Cloudflare 3.8.4

  5. Cloudflare 3.8.3

  6. Cloudflare 3.8.2

  7. Cloudflare 3.8.1

  8. Cloudflare 3.8.0

  9. Cloudflare 3.7.0

  10. Cloudflare 3.6.0

  11. Cloudflare 3.5.1

  12. Cloudflare 3.5.0

20193 releases

  1. Cloudflare 3.4.1

  2. Cloudflare 3.4.0

  3. Cloudflare 3.3.3

20175 releases

  1. Cloudflare 3.3.2

  2. Cloudflare 3.3.1

  3. Cloudflare 3.3.0

  4. Cloudflare 3.2.1

  5. Cloudflare 3.2.0

201636 releases

  1. Cloudflare 3.1.1

  2. Cloudflare 3.1.0

  3. Cloudflare 3.0.6

  4. Cloudflare 3.0.5

  5. Cloudflare 3.0.4

  6. Cloudflare 3.0.3

  7. Cloudflare 3.0.2

  8. Cloudflare 3.0.1

  9. Cloudflare 3.0.0

  10. Cloudflare 1.3.25

  11. Cloudflare 1.3.24

  12. Cloudflare 1.3.23

  13. Cloudflare 1.3.22

  14. Cloudflare 1.3.21

  15. Cloudflare 1.3.20

  16. Cloudflare 1.3.19

  17. Cloudflare 1.3.18

  18. Cloudflare 1.3.17

  19. Cloudflare 1.3.16

  20. Cloudflare 1.3.15

  21. Cloudflare 1.3.14

  22. Cloudflare 1.3.13

  23. Cloudflare 1.3.12

  24. Cloudflare 1.3.11

  25. Cloudflare 1.3.10

  26. Cloudflare 1.3.9

  27. Cloudflare 1.3.8

  28. Cloudflare 1.3.7

  29. Cloudflare 1.3.6

  30. Cloudflare 1.3.5

  31. Cloudflare 1.3.4

  32. Cloudflare 1.3.3

  33. Cloudflare 1.3.2.Beta

  34. Cloudflare 1.2.6.Beta

  35. Cloudflare 1.2.5.Beta

  36. Cloudflare 1.2.4

Questions about Cloudflare’s releases

What is the latest version of Cloudflare?

4.14.5, released on Oct 5, 2026 (1 month ago). It’s tested up to WordPress 7.1.4 and needs PHP 7.4 or later.

How often is Cloudflare updated?

6 releases in the last year, about one every 58 days. Its first release on WordPress.org dates from September 2016.

Know when your rivals ship

Track your plugin and its rivals: TrackWP sees each new release in the nightly snapshot and alerts you, with what it did to their rank.

Start free

Release dates come from the day each version’s folder was made in Cloudflare’s WordPress.org SVN repository; the notes from its readme’s changelog, as its authors wrote it.