How many CVEs have patched get_site_transient?

1 published CVEs changed get_site_transient in wordpress/core, in 1 distinct patches totalling 4 changed lines, between 2024 and 2024.

What is the latest CVE that changed get_site_transient?

CVE-2023-5692 (WordPress Core <= 6.4.3 - Sensitive Information Exposure via redirect_guess_404_permalink), published 2024-04-05, changed lines 2518 to 2520 of trunk/wp-includes/option.php.

How does get_site_transient compare to the rest of wordpress/core?

wordpress/core has 73 CVEs with a located fix in total; 1 of them changed get_site_transient.

What do the line numbers refer to?

Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

RadicalNotion.AI

Log in Create an account

wordpress/core

Function

get_site_transient

Name: get_site_transient in wordpress/core: CVE fixes
Creator: RadicalNotion.AI
License: https://creativecommons.org/licenses/by-nc/4.0/

trunk/wp-includes/option.php

Last patched April 5, 2024

1

CVEs

That changed this function

1

Distinct patches

Backports counted once

4

Lines changed

Added plus removed

2024

Years

By CVE publication date

Overview

get_site_transient in wordpress/core was changed by 1 published CVE fixes in 2024, in 1 distinct patches that added or removed 4 lines in total.

wordpress/core has 73 CVEs with a located fix in total, so 1% of them touched this function.

CVEs that patched it

Every published CVE whose fix changed get_site_transient, newest first, with the lines each fix touched.

WordPress Core <= 6.4.3 - Sensitive Information Exposure via redirect_guess_404_permalink
CVE-2023-5692 · lines 2518–2520 · +3 −1
Medium · CVSS 5.3
EPSS 0.8%2024-04-05

Get an alert when the next CVE fix lands in wordpress/core, with the patched functions.

Monitor core CVEs

Other functions in these files

Functions in the same file that CVE fixes also changed.

Other hotspots in the repository

Functions in wordpress/core changed by the most CVE fixes.

wp_version_check2 CVEs · trunk/wp-includes/update.php do_shortcodes_in_html_tags2 CVEs · branches/3.7/wp-includes/shortcodes.php wpmu_activate_stylesheet2 CVEs · trunk/wp-activate.php maybe_create_table2 CVEs · trunk/wp-admin/includes/upgrade.php upgrade_4002 CVEs · trunk/wp-admin/includes/upgrade.php translations_api2 CVEs · trunk/wp-admin/includes/translation-install.php

All patched functions in wordpress/core

Frequently asked questions

Common questions about CVE fixes to get_site_transient.

How many CVEs have patched get_site_transient?: 1 published CVEs changed get_site_transient in wordpress/core, in 1 distinct patches totalling 4 changed lines, between 2024 and 2024.
What is the latest CVE that changed get_site_transient?: CVE-2023-5692 (WordPress Core <= 6.4.3 - Sensitive Information Exposure via redirect_guess_404_permalink), published 2024-04-05, changed lines 2518 to 2520 of trunk/wp-includes/option.php.
How does get_site_transient compare to the rest of wordpress/core?: wordpress/core has 73 CVEs with a located fix in total; 1 of them changed get_site_transient.
What do the line numbers refer to?: Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

References

Fix locations are computed by RadicalNotion.AI from the upstream patch diff of each CVE. CVE data is sourced from the CVE Program.

Track wordpress/core CVEs

Get an alert when a new CVE lands in this repository, with the patched functions and AI-written remediation guidance.

Create an account See pricing