Wordfence Premium Activator icon

5 versions

Wordfence Premium Activator history.

Every release of Wordfence Premium Activator is archived here with its changelog, file size, and security scan result. Use the archive to roll back to a stable release or audit what changed between updates.

3 of 5 releases scanned clean
v2.6.4Latest
July 13, 20266.9 KBScanned
* Rebased onto upstream 2.6.3 code. * Adds hourly suppression of the Wordfence "WAF rules update unsuccessful" admin warning (cosmetic — does not fetch rules). * GPLCoffee rebrand. * Version bumped to 2.6.4 to supersede the earlier 2.6.3-labeled build, which carried older code.
May 31, 20265.9 KBScanned
Fixed
  • `wfCentralAPIException: Wordfence Central secret key has not been created yet` flooding the server error log
  • duplicate entry SQL error for `scan_exclude` when the row exists with a NULL value
  • scan exclusion not being applied due to the above INSERT failure blocking the UPDATE path
Added
  • `pre_http_request` filter (priority 1) intercepting all calls to `https://www.wordfence.com/api/wf` — nonce endpoint returns `{"nonce":"..."}`, token endpoint returns a fake JWT, all other endpoints return `{"data":{}}` 200 OK; does not affect scanning or firewall (those use `noc1.wordfence.com`)
Other
  • Generated a real libsodium keypair on first load (`wordfenceCentralSecretKey`) so `fetchToken()` can complete the sign-nonce flow if the JWT transient ever expires
  • Pre-seeded `wordfenceCentralJWT` transient with a long-lived fake JWT (exp ≈ year 2065) so `fetchToken()` is bypassed on normal requests
  • Replaced SELECT + conditional INSERT/UPDATE with atomic INSERT ON DUPLICATE KEY UPDATE to eliminate race condition
  • Corrected scan exclusion path from `/wordfence-activator/*` to `wp-content/plugins/wordfence-activator/*` to match Wordfence's ABSPATH-relative filename format used in wfScanner
May 12, 20263.9 KBScanned
Fixed
  • "Response License Expiring" banner caused by keyExpDays never being written to the database
  • "Auto-renew is disabled" warning by persisting premiumAutoRenew to the database
  • licenseType and keyType not surviving page reloads (were set in-memory only, never persisted)
  • stale keyType cache in wfLicense singleton by calling save() to trigger clearCache() and re-resolution
Added
  • explicit zeroing of all payment warning flags (premiumPaymentExpiring, Expired, Missing, Hold)
  • Wordfence Central connected state (wordfenceCentralConnected, SiteID, ConnectTime, ConnectEmail)
Other
  • Flush wfCentral::_isConnected() static cache so connected state is reflected within the same request
  • Compatibility with Wordfence 8.2.x
v2.5.0Unavailable
September 10, 20252.9 KBUnknown
Added
  • multisite support
  • table existence check before database operations
Fixed
  • database errors in multisite installations
Other
  • Prevented duplicate entries in scan exclusion list
v2.4.3Unavailable
May 13, 20252.2 KBUnknown

Why archive

Sometimes the latest release isn't the one you need. The archive lets you pin Wordfence Premium Activator to a known-good version, or roll back while a bug is investigated. Every release stays scanned and reachable.