Skip to main content

Pantheon release notes

Your destination for staying informed about our latest innovations and product updates.
Subscribe to RSS feed

WordPress
November 18, 2026

Pantheon now provides WordPress 7.1.5, a security release that fixes 20 issues in WordPress core.

Action required

Update your sites to WordPress 7.1.5 as soon as possible. Apply the update from your Pantheon dashboard or with Terminus. See how to apply core updates.

Pantheon deployed Web Application Firewall (WAF) protection in advance for some of the vulnerabilities this release fixes. The WAF rules do not replace the update, so update your sites as soon as possible.

This release fixes 20 security issues

Vulnerabilities that attackers can exploit without logging in:

  • Privilege escalation through Template Part block attributes, which could lead to remote code execution.
  • Stored cross-site scripting (XSS) through shortcode attributes in comments.
  • Denial of service through batched XML-RPC pingbacks.
  • Private taxonomy terms exposed through the REST API search endpoint.

Other vulnerabilities:

  • SQL injection in WP_Meta_Query through nested relation values.
  • SQL injection through the front page setting in Customizer changeset previews.
  • Privilege escalation from site Administrator to Super Admin on multisite through Customizer menu previews.
  • Stored XSS by users with the Contributor role or higher in the Comment Date block, in oEmbed provider responses, and in the block editor through media filenames.
  • Stored XSS by Administrators through Customizer previews.
  • XSS in wp_interactivity_data_wp_context() through the store namespace.
  • XSS in the block editor through Openverse image metadata.
  • Reflected XSS in the legacy media library popup.
  • Authorization bypass by users with the Author role or higher through comment editing in the admin.
  • User email addresses exposed to users with the Author role or higher through the REST API comments endpoint.
  • Information disclosure by users with the Editor role or higher through post and template author assignment in the REST API.
  • Information disclosure by Subscribers through XML-RPC wp.getComments.

Hardening changes:

  • WordPress now matches JSON media types with a corrected regular expression.
  • WordPress removes the block editor's Imgur embed variation, because its server-side provider no longer exists.

This release also removes 1024-bit certificates from the bundled root certificates in WordPress 6.9.12 and earlier. WordPress 7.0 already removed them.

Dependabot commits in the release history

The release history includes two commits that manage .github/dependabot.yml. Pantheon added them by mistake. The first commit adds the file and the next commit removes it, so applying the update makes no net change to your site.

For full details, see the WordPress 7.1.5 release announcement.

November 4, 2026

Version 1.4.3 of the Pantheon Content Publisher WordPress plugin is now available.

What's new?

  • Smoother video previews — Embedded videos no longer reload or flicker in the real-time preview every time you make an edit.
  • Fresher preview links — Preview links now always show your latest content instead of a cached, out-of-date version.
  • More reliable Smart Components — All Smart Components on the page, not just videos, now stay visible in the real-time preview as you keep editing.
  • Clearer preview errors — If the real-time preview can't load your latest edits, you'll see a clear error message instead of outdated content.

Update to 1.4.3 from the WordPress dashboard under Plugins > Installed Plugins, or download it from the WordPress Plugin Repository.

For more details, see the plugin changelog.

October 28, 2026

The latest security release for WordPress, 7.1.4, is available on Pantheon.

Action required

Because this is a security update, we recommend all users upgrade to WordPress 7.1.4 as soon as possible from your Pantheon dashboard or Terminus to access the latest features, fixes, and security enhancements. See related documentation for how to apply core updates.

Pantheon has deployed platform-wide mitigations against external abuse of some of the vulnerabilities fixed in this release, and is actively monitoring those rules. However, customers need to update their sites as soon as possible.

Highlights

This release resolves 13 security issues:

  • A remote code execution weakness in the upgrade process.
  • Stored XSS via specially crafted block markup.
  • Stored XSS in privacy data removal requests.
  • Multiple stored XSS issues in the Interactivity API.
  • A stored denial of service in the Interactivity API.
  • Stored XSS in Customizer selective refresh.
  • Stored XSS in the Categories block.
  • Stored XSS in user login fields.
  • Unauthenticated disclosure of unpublished Customizer changesets.
  • Stored XSS in the Playlist and Image blocks.
  • Stored XSS in the Comments pagination blocks.
  • Notes readable by unauthorized privileged users, allowing privilege escalation.

This release also updates the bundled certificates to account for the revocation of an eMudhra root certificate.

For full details, see the WordPress 7.1.4 release announcement.

October 6, 2026

The latest security release for WordPress, 7.1.3, is available on Pantheon.

Action required

Because this is a security update, we recommend all users upgrade to WordPress 7.1.3 as soon as possible from your Pantheon dashboard or Terminus to access the latest features, fixes, and security enhancements. See related documentation for how to apply core updates.

Pantheon has deployed a platform-wide mitigation (virtual patching via our routing network) against external abuse of the stored XSS on the Comments administration page, and is actively monitoring that rule. However, customers need to update their sites as soon as possible.

Highlights

This release resolves seven security vulnerabilities:

  • A stored XSS on the Comments administration page, exploitable via pending comments.
  • A DoS issue in the WP_Http::make_absolute_url() method.
  • A second-order SQL injection in WordPress WXR export.
  • A weakness allowing Author role users to sticky posts.
  • Unauthenticated disclosure of comments on private and unpublished posts.
  • Imgur embeds are vulnerable to XSS.
  • Forgeable parameters passed to the {status}_{type} hook can lead to action name collision.

For full details, see the WordPress 7.1.3 release notes and WordPress documentation.

October 2, 2026

The 1.34.0 update is now available for the WordPress (composer managed) upstream. This update changes the default PHP version to 8.3, syncs the upstream with Roots Bedrock, and fixes a PHP warning. The Bedrock sync changes the Composer repository defaults, which can cause merge conflicts in your composer.json file.

Updates

  • Updates the default PHP version to 8.3 and changes the PHP requirement in composer.json to >=8.3. For more information about the PHP default change, see New default PHP version 8.3 for WordPress upstreams. (For more information see #204.)
  • Syncs the upstream with Bedrock. (For more information see #201.) This includes:
    • Changing the Composer repository from WPackagist (wpackagist.org) to WP Packages (repo.wp-packages.org). Package names for plugins and themes change from wpackagist-plugin/* and wpackagist-theme/* to wp-plugin/* and wp-theme/*.
    • Removing the roots/wp-password-bcrypt package from composer.json.
    • Setting WP_ENVIRONMENT_TYPE from WP_ENV when it is not already defined, and setting WP_DEVELOPMENT_MODE when it is configured.
    • Setting MYSQL_CLIENT_FLAGS to use SSL when DB_SSL is set.

Bug fixes

  • Resolves a rtrim() warning in PHP 8.1 and later environments. (For more information see #189. Props @mattmacneil.)

For more details, refer to the WordPress (Composer Managed) changelog.

Action required

To benefit from these updates and ensure your site is using the most current version, apply the update to your WordPress (composer managed) site or custom upstream.

If your composer.json file requires plugins or themes using wpackagist-plugin/* or wpackagist-theme/* package names, or has custom entries in repositories, applying this update can cause merge conflicts in that file. When you resolve the conflicts, keep your custom requirements and update the package names to the new wp-plugin/* and wp-theme/* names, or keep the WPackagist repository entry.

For assistance with managing merge conflicts, refer to our documentation on auto-resolving via the dashboard or manually resolving via the command line.

October 2, 2026

Pantheon has updated the default PHP version for the WordPress and WordPress (composer managed) upstreams to PHP 8.3, replacing the previous default of PHP 8.2.

New sites created from these upstreams use PHP 8.3. Existing sites that do not set php_version in their own pantheon.yml move to PHP 8.3 when they apply this upstream update.

Action required

Test the update before you deploy it to the Live environment. Apply it in Dev or a Multidev environment, confirm your plugins and theme work on PHP 8.3, then promote it.

If your site needs to stay on PHP 8.2, pin the version by setting php_version: 8.2 in your site's pantheon.yml before you apply the update. For steps, see Manage PHP Versions.

If you maintain a custom upstream, this change is not reflected in your pantheon.upstream.yml unless you update your fork from Pantheon's upstream.

September 30, 2026

Version 1.4.1 of the Pantheon Content Publisher WordPress plugin is now available.

What's new?

Improved how Smart Components are placed in your posts and pages, including in the Content Publisher preview. #261

Update to 1.4.1 from the WordPress dashboard under Plugins > Installed Plugins, or download it from the WordPress Plugin Repository.

For more details, see the plugin changelog.

September 22, 2026

The latest security release for WordPress, 7.1.2, is available on Pantheon.

Action required

Because this is a security update, we recommend all users upgrade to WordPress 7.1.2 as soon as possible from your Pantheon dashboard or Terminus to access the latest features, fixes, and security enhancements. See related documentation for how to apply core updates.

Pantheon has pre-deployed platform-wide mitigations (virtual patching via our routing network) against external abuse of this vulnerability (CVE-2026-87902), and is actively monitoring those rules. However, customers need to update their sites as soon as possible.

Highlights

This release resolves one critical severity vulnerability (CVE-2026-87902) that does not require authentication to exploit. Under certain server and theme conditions, an unauthenticated attacker can cause page template resolution to include a chosen readable local PHP file outside the active theme directories, which could potentially lead to remote code execution.

For full details, see the WordPress 7.1.2 release notes and WordPress documentation.