#62811 (Update bundled root certificates for 6.8) – WordPress Trac

Works for me. My initial thinking was to separate the build process and the actual update of the certificates. But don't feel strongly about that at all.

#10 @desrosj
18 months ago

In 59740:

Security: Introduce Grunt task for updating Root Certificates.

The Root Certificate bundle maintained by Mozilla ships in WordPress to allow SSL certificates to be verified on hosts with incomplete, outdated, or invalid local SSL configurations. To date, updates have only been merged into Core when problems arise using a highly manual process.

This introduces the certificates:upgrade Grunt task to automate the process of updating the included bundle with upstream changes using Composer to manage versioning.

The legacy 1024bit certificates included for backwards compatibility are now maintained in a separate file that is prepended to the built version of the bundle during the relevant Grunt tasks. Some expired certificates from this list have been removed:

Cybertrust Global Root (expired 2021-12-15)
Thawte Server CA (expired 2020-12-31)
Thawte Premium Server CA (expired 2020-12-31)

The Dependabot configuration has also been updated to open pull requests when new releases occur upstream. Going forward, the recommendation is to create a task ticket for updating these certificates with each release when an update is published. See #62811 for an example of this.

Props johnbillion, desrosj, whyisjake, ayeshrajans, SergeyBiryukov, swissspidy, skithund, barry.
Fixes #62812. See #62811, 50828.

#11 @johnbillion
18 months ago

Resolution → fixed
Status new → closed

#12 @desrosj
17 months ago

Resolution fixed
Status closed → reopened

Looks like there is a 1.5.6 update available.

This ticket was mentioned in PR #8489 on WordPress/wordpress-develop by @desrosj.

17 months ago #13

Trac ticket: https://core.trac.wordpress.org/ticket/62811

#14 @desrosj
16 months ago

Owner set to desrosj
Resolution → fixed
Status reopened → closed

In 59969:

Security: Update composer/ca-bundle to version 1.5.6.

Follow up to [59740].

Fixes #62811.

#15 @desrosj
16 months ago

In 59974:

Security: Update bundled Root Certificates.

The Root Certificate bundle maintained by Mozilla ships in WordPress to allow SSL certificates to be verified on hosts with incomplete, outdated, or invalid local SSL configurations.

This updates the ca-bundle.crt file to the latest version, which applies upstream changes from the bundle maintained by Mozilla and keeps all unexpired legacy 1024bit certificates which are kept for backward compatibility purposes (see [35919]).

Partially merges [59740] and [59969] to the 6.7 branch.

See #62811, #62711.

#16 @desrosj
16 months ago

In 59994:

Security: Update bundled Root Certificates.

The Root Certificate bundle maintained by Mozilla ships in WordPress to allow SSL certificates to be verified on hosts with incomplete, outdated, or invalid local SSL configurations.

This updates the ca-bundle.crt file to the latest version, which applies upstream changes from the bundle maintained by Mozilla and keeps all unexpired legacy 1024bit certificates which are kept for backward compatibility purposes (see [35919]).

Partially merges [59740] and [59969] to the 6.6 branch.

Props johnbillion, desrosj, whyisjake, ayeshrajans, SergeyBiryukov, swissspidy, skithund, barry.
See #62811, #62711.

#17 @desrosj
16 months ago

In 59995:

Security: Update bundled Root Certificates.

The Root Certificate bundle maintained by Mozilla ships in WordPress to allow SSL certificates to be verified on hosts with incomplete, outdated, or invalid local SSL configurations.

This updates the ca-bundle.crt file to the latest version, which applies upstream changes from the bundle maintained by Mozilla and keeps all unexpired legacy 1024bit certificates which are kept for backward compatibility purposes (see [35919]).

Partially merges [59740] and [59969] to the 6.5 branch.

Props johnbillion, desrosj, whyisjake, ayeshrajans, SergeyBiryukov, swissspidy, skithund, barry.
See #62811, #62711.

#18 @desrosj
16 months ago

In 59996:

Security: Update bundled Root Certificates.

The Root Certificate bundle maintained by Mozilla ships in WordPress to allow SSL certificates to be verified on hosts with incomplete, outdated, or invalid local SSL configurations.

This updates the ca-bundle.crt file to the latest version, which applies upstream changes from the bundle maintained by Mozilla and keeps all unexpired legacy 1024bit certificates which are kept for backward compatibility purposes (see [35919]).

Partially merges [59740] and [59969] to the 6.4 branch.

Props johnbillion, desrosj, whyisjake, ayeshrajans, SergeyBiryukov, swissspidy, skithund, barry.
See #62811, #62711.

#19 @desrosj
16 months ago

In 59997:

Security: Update bundled Root Certificates.

The Root Certificate bundle maintained by Mozilla ships in WordPress to allow SSL certificates to be verified on hosts with incomplete, outdated, or invalid local SSL configurations.

This updates the ca-bundle.crt file to the latest version, which applies upstream changes from the bundle maintained by Mozilla and keeps all unexpired legacy 1024bit certificates which are kept for backward compatibility purposes (see [35919]).

Partially merges [59740] and [59969] to the 6.3 branch.

Props johnbillion, desrosj, whyisjake, ayeshrajans, SergeyBiryukov, swissspidy, skithund, barry.
See #62811, #62711.

#20 @desrosj
16 months ago

In 59998:

Security: Update bundled Root Certificates.

The Root Certificate bundle maintained by Mozilla ships in WordPress to allow SSL certificates to be verified on hosts with incomplete, outdated, or invalid local SSL configurations.

This updates the ca-bundle.crt file to the latest version, which applies upstream changes from the bundle maintained by Mozilla and keeps all unexpired legacy 1024bit certificates which are kept for backward compatibility purposes (see [35919]).

Partially merges [59740] and [59969] to the 6.2 branch.

Props johnbillion, desrosj, whyisjake, ayeshrajans, SergeyBiryukov, swissspidy, skithund, barry.
See #62811, #62711.

#21 @desrosj
16 months ago

In 59999:

Security: Update bundled Root Certificates.

The Root Certificate bundle maintained by Mozilla ships in WordPress to allow SSL certificates to be verified on hosts with incomplete, outdated, or invalid local SSL configurations.

This updates the ca-bundle.crt file to the latest version, which applies upstream changes from the bundle maintained by Mozilla and keeps all unexpired legacy 1024bit certificates which are kept for backward compatibility purposes (see [35919]).

Partially merges [59740] and [59969] to the 6.1 branch.

Props johnbillion, desrosj, whyisjake, ayeshrajans, SergeyBiryukov, swissspidy, skithund, barry.
See #62811, #62711.

#22 @desrosj
16 months ago

In 60000:

Security: Update bundled Root Certificates.

🎵 60,000 certs on the wall. 60,000 certs. Take one down, pass it around, 59,999 certs on the wall. 🎵

The Root Certificate bundle maintained by Mozilla ships in WordPress to allow SSL certificates to be verified on hosts with incomplete, outdated, or invalid local SSL configurations.

This updates the ca-bundle.crt file to the latest version, which applies upstream changes from the bundle maintained by Mozilla and keeps all unexpired legacy 1024bit certificates which are kept for backward compatibility purposes (see [35919]).

This equals alot of certificates.

Partially merges [59740] and [59969] to the 6.0 branch.

Props johnbillion, desrosj, whyisjake, ayeshrajans, SergeyBiryukov, swissspidy, skithund, barry, joedolson.
Fixes #60000. See #62811, #62711.

#23 @desrosj
16 months ago

In 60001:

Security: Update bundled Root Certificates.

The Root Certificate bundle maintained by Mozilla ships in WordPress to allow SSL certificates to be verified on hosts with incomplete, outdated, or invalid local SSL configurations.

This updates the ca-bundle.crt file to the latest version, which applies upstream changes from the bundle maintained by Mozilla and keeps all unexpired legacy 1024bit certificates which are kept for backward compatibility purposes (see [35919]).

Partially merges [59740] and [59969] to the 5.9 branch.

Props johnbillion, desrosj, whyisjake, ayeshrajans, SergeyBiryukov, swissspidy, skithund, barry.
See #62811, #62711.

#24 @desrosj
16 months ago

In 60002:

Security: Update bundled Root Certificates.

The Root Certificate bundle maintained by Mozilla ships in WordPress to allow SSL certificates to be verified on hosts with incomplete, outdated, or invalid local SSL configurations.

This updates the ca-bundle.crt file to the latest version, which applies upstream changes from the bundle maintained by Mozilla and keeps all unexpired legacy 1024bit certificates which are kept for backward compatibility purposes (see [35919]).

Partially merges [59740] and [59969] to the 5.8 branch.

Props johnbillion, desrosj, whyisjake, ayeshrajans, SergeyBiryukov, swissspidy, skithund, barry.
See #62811, #62711.

#25 @desrosj
16 months ago

In 60013:

Security: Update bundled Root Certificates.

The Root Certificate bundle maintained by Mozilla ships in WordPress to allow SSL certificates to be verified on hosts with incomplete, outdated, or invalid local SSL configurations.

This updates the ca-bundle.crt file to the latest version, which applies upstream changes from the bundle maintained by Mozilla and keeps all unexpired legacy 1024bit certificates which are kept for backward compatibility purposes (see [35919]).

Partially merges [59740] and [59969] to the 5.7 branch.

Props johnbillion, desrosj, whyisjake, ayeshrajans, SergeyBiryukov, swissspidy, skithund, barry.
See #62811, #62711.

#26 @desrosj
16 months ago

In 60014:

Security: Update bundled Root Certificates.

The Root Certificate bundle maintained by Mozilla ships in WordPress to allow SSL certificates to be verified on hosts with incomplete, outdated, or invalid local SSL configurations.

This updates the ca-bundle.crt file to the latest version, which applies upstream changes from the bundle maintained by Mozilla and keeps all unexpired legacy 1024bit certificates which are kept for backward compatibility purposes (see [35919]).

Partially merges [59740] and [59969] to the 5.6 branch.

Props johnbillion, desrosj, whyisjake, ayeshrajans, SergeyBiryukov, swissspidy, skithund, barry.
See #62811, #62711.

#27 @desrosj
16 months ago

In 60015:

Security: Update bundled Root Certificates.

The Root Certificate bundle maintained by Mozilla ships in WordPress to allow SSL certificates to be verified on hosts with incomplete, outdated, or invalid local SSL configurations.

This updates the ca-bundle.crt file to the latest version, which applies upstream changes from the bundle maintained by Mozilla and keeps all unexpired legacy 1024bit certificates which are kept for backward compatibility purposes (see [35919]).

Partially merges [59740] and [59969] to the 5.5 branch.

Props johnbillion, desrosj, whyisjake, ayeshrajans, SergeyBiryukov, swissspidy, skithund, barry.
See #62811, #62711.

#28 @desrosj
16 months ago

In 60016:

Security: Update bundled Root Certificates.

The Root Certificate bundle maintained by Mozilla ships in WordPress to allow SSL certificates to be verified on hosts with incomplete, outdated, or invalid local SSL configurations.

This updates the ca-bundle.crt file to the latest version, which applies upstream changes from the bundle maintained by Mozilla and keeps all unexpired legacy 1024bit certificates which are kept for backward compatibility purposes (see [35919]).

Partially merges [48707], [59740] and [59969] to the 5.4 branch.

Props johnbillion, desrosj, whyisjake, ayeshrajans, SergeyBiryukov, swissspidy, skithund, barry.
See #62811, #62711, #50828.

#29 @desrosj
16 months ago

In 60017:

Security: Update bundled Root Certificates.

The Root Certificate bundle maintained by Mozilla ships in WordPress to allow SSL certificates to be verified on hosts with incomplete, outdated, or invalid local SSL configurations.

This updates the ca-bundle.crt file to the latest version, which applies upstream changes from the bundle maintained by Mozilla and keeps all unexpired legacy 1024bit certificates which are kept for backward compatibility purposes (see [35919]).

Partially merges [48707], [59740] and [59969] to the 5.3 branch.

Props johnbillion, desrosj, whyisjake, ayeshrajans, SergeyBiryukov, swissspidy, skithund, barry.
See #62811, #62711, #50828.

#30 @desrosj
16 months ago

In 60018:

Security: Update bundled Root Certificates.

The Root Certificate bundle maintained by Mozilla ships in WordPress to allow SSL certificates to be verified on hosts with incomplete, outdated, or invalid local SSL configurations.

This updates the ca-bundle.crt file to the latest version, which applies upstream changes from the bundle maintained by Mozilla and keeps all unexpired legacy 1024bit certificates which are kept for backward compatibility purposes (see [35919]).

Partially merges [46094], [48707], [59740] and [59969] to the 5.2 branch.

See #62811, #62711, #50828, #45807.

#31 @desrosj
16 months ago

In 60019:

Security: Update bundled Root Certificates.

The Root Certificate bundle maintained by Mozilla ships in WordPress to allow SSL certificates to be verified on hosts with incomplete, outdated, or invalid local SSL configurations.

This updates the ca-bundle.crt file to the latest version, which applies upstream changes from the bundle maintained by Mozilla and keeps all unexpired legacy 1024bit certificates which are kept for backward compatibility purposes (see [35919]).

Partially merges [46094], [58707], [59740] and [59969] to the 5.1 branch.

See #62811, #62711, #50828, #45807.

#32 @desrosj
16 months ago

In 60020:

Security: Update bundled Root Certificates.

The Root Certificate bundle maintained by Mozilla ships in WordPress to allow SSL certificates to be verified on hosts with incomplete, outdated, or invalid local SSL configurations.

This updates the ca-bundle.crt file to the latest version, which applies upstream changes from the bundle maintained by Mozilla and keeps all unexpired legacy 1024bit certificates which are kept for backward compatibility purposes (see [35919]).

Partially merges [46094], [58707], [59740] and [59969] to the 5.0 branch.

See #62811, #62711, #50828, #45807.

#33 @desrosj
16 months ago

In 60021:

Security: Update bundled Root Certificates.

The Root Certificate bundle maintained by Mozilla ships in WordPress to allow SSL certificates to be verified on hosts with incomplete, outdated, or invalid local SSL configurations.

This updates the ca-bundle.crt file to the latest version, which applies upstream changes from the bundle maintained by Mozilla and keeps all unexpired legacy 1024bit certificates which are kept for backward compatibility purposes (see [35919]).

Partially merges [46094], [58707], [59740] and [59969] to the 4.9 branch.

See #62811, #62711, #50828, #45807.

#34 @desrosj
16 months ago

In 60022:

Security: Update bundled Root Certificates.

The Root Certificate bundle maintained by Mozilla ships in WordPress to allow SSL certificates to be verified on hosts with incomplete, outdated, or invalid local SSL configurations.

This updates the ca-bundle.crt file to the latest version, which applies upstream changes from the bundle maintained by Mozilla and keeps all unexpired legacy 1024bit certificates which are kept for backward compatibility purposes (see [35919]).

Partially merges [46094], [58707], [59740] and [59969] to the 4.8 branch.

See #62811, #62711, #50828, #45807.

#35 @desrosj
16 months ago

In 60023:

Security: Update bundled Root Certificates.

The Root Certificate bundle maintained by Mozilla ships in WordPress to allow SSL certificates to be verified on hosts with incomplete, outdated, or invalid local SSL configurations.

This updates the ca-bundle.crt file to the latest version, which applies upstream changes from the bundle maintained by Mozilla and keeps all unexpired legacy 1024bit certificates which are kept for backward compatibility purposes (see [35919]).

Partially merges [46094], [58707], [59740] and [59969] to the 4.7 branch.

See #62811, #62711, #50828, #45807.

#36 @desrosj
16 months ago

In 60024:

Security: Update bundled Root Certificates.

The Root Certificate bundle maintained by Mozilla ships in WordPress to allow SSL certificates to be verified on hosts with incomplete, outdated, or invalid local SSL configurations.

This updates the ca-bundle.crt file to the latest version, which applies upstream changes from the bundle maintained by Mozilla and keeps all unexpired legacy 1024bit certificates which are kept for backward compatibility purposes (see [35919]).

Partially merges [46094], [58707], [59740] and [59969] to the 4.6 branch.

See #62811, #62711, #50828, #45807.

#37 @desrosj
16 months ago

In 60025:

Security: Update bundled Root Certificates.

The Root Certificate bundle maintained by Mozilla ships in WordPress to allow SSL certificates to be verified on hosts with incomplete, outdated, or invalid local SSL configurations.

This updates the ca-bundle.crt file to the latest version, which applies upstream changes from the bundle maintained by Mozilla and keeps all unexpired legacy 1024bit certificates which are kept for backward compatibility purposes (see [35919]).

Partially merges [37431], [46094], [58707], [59740] and [59969] to the 4.5 branch.

Props johnbillion, desrosj, whyisjake, ayeshrajans, SergeyBiryukov, swissspidy, skithund, barry, paragoninitiativeenterprises, ocean90, DrewAPicture.
See #62811, #62711, #50828, #45807, #36835.

#38 @desrosj
16 months ago

In 60026:

Security: Update bundled Root Certificates.

The Root Certificate bundle maintained by Mozilla ships in WordPress to allow SSL certificates to be verified on hosts with incomplete, outdated, or invalid local SSL configurations.

This updates the ca-bundle.crt file to the latest version, which applies upstream changes from the bundle maintained by Mozilla and keeps all unexpired legacy 1024bit certificates which are kept for backward compatibility purposes (see [35919]).

Partially merges [37431], [496094], [58707], [59740] and [59969] to the 4.4 branch.

Props johnbillion, desrosj, whyisjake, ayeshrajans, SergeyBiryukov, swissspidy, skithund, barry, paragoninitiativeenterprises, ocean90, DrewAPicture.
See #62811, #62711, #50828, #45807, #36835.

#39 @desrosj
16 months ago

In 60027:

Security: Update bundled Root Certificates.

The Root Certificate bundle maintained by Mozilla ships in WordPress to allow SSL certificates to be verified on hosts with incomplete, outdated, or invalid local SSL configurations.

This updates the ca-bundle.crt file to the latest version, which applies upstream changes from the bundle maintained by Mozilla and keeps all unexpired legacy 1024bit certificates which are kept for backward compatibility purposes (see [35919]).

Partially merges [34283], [35919], [36570], [37431], [46094], [58707], [59740] and [59969] to the 4.3 branch.

Props johnbillion, desrosj, whyisjake, ayeshrajans, SergeyBiryukov, swissspidy, skithund, barry, paragoninitiativeenterprises, ocean90, DrewAPicture, dd32, rmccue.
See #62811, #62711, #50828, #45807, #36835, #34935.

#40 @desrosj
16 months ago

In 60028:

Security: Update bundled Root Certificates.

The Root Certificate bundle maintained by Mozilla ships in WordPress to allow SSL certificates to be verified on hosts with incomplete, outdated, or invalid local SSL configurations.

This updates the ca-bundle.crt file to the latest version, which applies upstream changes from the bundle maintained by Mozilla and keeps all unexpired legacy 1024bit certificates which are kept for backward compatibility purposes (see [35919]).

Partially merges [34283], [35919], [36570], [37431], [46094], [58707], [59740] and [59969] to the 4.2 branch.

Props johnbillion, desrosj, whyisjake, ayeshrajans, SergeyBiryukov, swissspidy, skithund, barry, paragoninitiativeenterprises, ocean90, DrewAPicture, dd32, rmccue.
See #62811, #62711, #50828, #45807, #36835, #34935.

#41 @desrosj
16 months ago

In 60029:

Security: Update bundled Root Certificates.

The Root Certificate bundle maintained by Mozilla ships in WordPress to allow SSL certificates to be verified on hosts with incomplete, outdated, or invalid local SSL configurations.

This updates the ca-bundle.crt file to the latest version, which applies upstream changes from the bundle maintained by Mozilla and keeps all unexpired legacy 1024bit certificates which are kept for backward compatibility purposes (see [35919]).

Partially merges [34283], [35919], [36570], [37431], [496094], [58707], [59740] and [59969] to the 4.1 branch.

Props johnbillion, desrosj, whyisjake, ayeshrajans, SergeyBiryukov, swissspidy, skithund, barry, paragoninitiativeenterprises, ocean90, DrewAPicture, dd32, rmccue.
Fixes #62711. See #62811, #50828, #45807, #36835, #34935.

#42 @desrosj
16 months ago

I've gone and opened #63165 for the 6.9 cycle.

This ticket was mentioned in PR #12023 on WordPress/wordpress-develop by XananasX7.

7 weeks ago #43

## Summary

Multiple unserialize() call sites in WordPress core pass no allowed_classes option, allowing PHP gadget-chain attacks (PHP Object Injection / POI) if an attacker can influence the serialized data. This PR adds allowed_classes => false to every call site where only scalar/array data is expected, and defense-in-depth to all HMAC-validated widget deserialization paths.

## Files Changed

### src/wp-includes/functions.php — maybe_unserialize()

This is the most impactful change. maybe_unserialize() is called in hundreds of places throughout WordPress core to decode option values (wp_options), user meta, post meta, and widget settings from the database. The stored values are always scalars, arrays, or simple objects — never complex class instances with destructors or magic methods. Passing allowed_classes => false prevents any gadget-chain exploitation without any functional change.

### Widget unserialize paths (4 files)

src/wp-includes/blocks/legacy-widget.php
src/wp-includes/rest-api/endpoints/class-wp-rest-widgets-controller.php
src/wp-includes/rest-api/endpoints/class-wp-rest-widget-types-controller.php
src/wp-includes/class-wp-customize-widgets.php

All four already validate the serialized data via wp_hash() / HMAC before deserializing. Defense-in-depth still applies: if a server-side key compromise or hash collision were exploited, allowed_classes => false provides a second layer. Widget instances are always plain array values.

### SimplePie cache backends (5 files)

src/wp-includes/SimplePie/src/Cache/Redis.php
src/wp-includes/SimplePie/src/Cache/Memcache.php
src/wp-includes/SimplePie/src/Cache/Memcached.php
src/wp-includes/SimplePie/src/Cache/File.php
src/wp-includes/SimplePie/src/Cache/MySQL.php

SimplePie stores RSS/Atom feed data as nested arrays of strings and integers — no PHP class instances. An attacker with write access to the Redis/Memcache/filesystem cache could inject a serialized gadget chain. allowed_classes => false closes this attack path on all five backends.

## Risk Without This Fix

PHP Object Injection via unserialize() is a well-documented RCE vector. WordPress's autoloader makes thousands of classes available at deserialization time, including many with __destruct() and __wakeup() methods that can be chained into arbitrary code execution (similar to exploits against Magento, Drupal, and Joomla in prior CVEs).

## Compatibility

allowed_classes => false causes unserialize() to return an __PHP_Incomplete_Class stub instead of instantiating unexpected classes. Since no call site in this PR is expected to produce PHP objects, there is no functional change for any legitimate WordPress installation or plugin. The only breakage would be a plugin that stores serialized class instances in a widget setting — an undocumented and unsupported pattern.

## References

https://owasp.org/www-community/vulnerabilities/PHP_Object_Injection
PHP unserialize() allowed_classes option: https://www.php.net/manual/en/function.unserialize.php
Google Open Source Security / Patch Rewards Program

Reported by:	desrosj	Owned by:	desrosj
Priority:	normal	Milestone:	6.8
Component:	Security	Version:
Severity:	normal	Keywords:	has-patch
Cc:		Focuses:

Make WordPress Core

Context Navigation

#62811 closed defect (bug) (fixed)

Update bundled root certificates for 6.8

Description (last modified by desrosj)

Change History (43)

This ticket was mentioned in ​PR #8134 on ​WordPress/wordpress-develop by ​@desrosj. 18 months ago #1

​@skithund commented on ​PR #8134: 18 months ago #2

​@desrosj commented on ​PR #8134: 18 months ago #3

#4 @desrosj 18 months ago

#5 @johnbillion 18 months ago

#6 @desrosj 18 months ago

#7 @desrosj 18 months ago

​@johnbillion commented on ​PR #8134: 18 months ago #8

​@desrosj commented on ​PR #8134: 18 months ago #9

#10 @desrosj 18 months ago

#11 @johnbillion 18 months ago

#12 @desrosj 17 months ago

This ticket was mentioned in ​PR #8489 on ​WordPress/wordpress-develop by ​@desrosj. 17 months ago #13

#14 @desrosj 16 months ago

#15 @desrosj 16 months ago

#16 @desrosj 16 months ago

#17 @desrosj 16 months ago

#18 @desrosj 16 months ago

#19 @desrosj 16 months ago

#20 @desrosj 16 months ago

#21 @desrosj 16 months ago

#22 @desrosj 16 months ago

#23 @desrosj 16 months ago

#24 @desrosj 16 months ago

#25 @desrosj 16 months ago

#26 @desrosj 16 months ago

#27 @desrosj 16 months ago

#28 @desrosj 16 months ago

#29 @desrosj 16 months ago

#30 @desrosj 16 months ago

#31 @desrosj 16 months ago

#32 @desrosj 16 months ago

#33 @desrosj 16 months ago

#34 @desrosj 16 months ago

#35 @desrosj 16 months ago

#36 @desrosj 16 months ago

#37 @desrosj 16 months ago

#38 @desrosj 16 months ago

#39 @desrosj 16 months ago

#40 @desrosj 16 months ago

#41 @desrosj 16 months ago

#42 @desrosj 16 months ago

This ticket was mentioned in ​PR #12023 on ​WordPress/wordpress-develop by ​XananasX7. 7 weeks ago #43

Download in other formats:

This ticket was mentioned in PR #8134 on WordPress/wordpress-develop by @desrosj.

18 months ago #1

@skithund commented on PR #8134:

18 months ago #2

@desrosj commented on PR #8134:

18 months ago #3

#4 @desrosj
18 months ago

#5 @johnbillion
18 months ago

#6 @desrosj
18 months ago

#7 @desrosj
18 months ago

@johnbillion commented on PR #8134:

18 months ago #8

@desrosj commented on PR #8134:

18 months ago #9

#10 @desrosj
18 months ago

#11 @johnbillion
18 months ago

#12 @desrosj
17 months ago

This ticket was mentioned in PR #8489 on WordPress/wordpress-develop by @desrosj.

17 months ago #13

#14 @desrosj
16 months ago

#15 @desrosj
16 months ago

#16 @desrosj
16 months ago

#17 @desrosj
16 months ago

#18 @desrosj
16 months ago

#19 @desrosj
16 months ago

#20 @desrosj
16 months ago

#21 @desrosj
16 months ago

#22 @desrosj
16 months ago

#23 @desrosj
16 months ago

#24 @desrosj
16 months ago

#25 @desrosj
16 months ago

#26 @desrosj
16 months ago

#27 @desrosj
16 months ago

#28 @desrosj
16 months ago

#29 @desrosj
16 months ago

#30 @desrosj
16 months ago

#31 @desrosj
16 months ago

#32 @desrosj
16 months ago

#33 @desrosj
16 months ago

#34 @desrosj
16 months ago

#35 @desrosj
16 months ago

#36 @desrosj
16 months ago

#37 @desrosj
16 months ago

#38 @desrosj
16 months ago

#39 @desrosj
16 months ago

#40 @desrosj
16 months ago

#41 @desrosj
16 months ago

#42 @desrosj
16 months ago

This ticket was mentioned in PR #12023 on WordPress/wordpress-develop by XananasX7.

7 weeks ago #43