How many CVEs have patched wp_get_available_translations?

2 published CVEs changed wp_get_available_translations in wordpress/core, in 1 distinct patches totalling 118 changed lines, between 2014 and 2014.

What is the latest CVE that changed wp_get_available_translations?

CVE-2014-5265, published 2014-08-18, changed lines 838 to 899 of trunk/wp-includes/l10n.php.

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

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

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

wp_get_available_translations

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

trunk/wp-includes/l10n.php

Last patched August 18, 2014

2

CVEs

That changed this function

1

Distinct patches

Backports counted once

118

Lines changed

Added plus removed

2014

Years

By CVE publication date

Overview

wp_get_available_translations in wordpress/core was changed by 2 published CVE fixes in 2014, in 1 distinct patches that added or removed 118 lines in total.

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

CVEs that patched it

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

CVE-2014-5265
CVE-2014-5265 · lines 838–899 · +50 −9
Medium · CVSS 5.0
EPSS 3.1%2014-08-18
CVE-2014-5266
CVE-2014-5266 · lines 838–899 · +50 −9
Medium · CVSS 5.0
EPSS 24.4%2014-08-18

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 wp_get_available_translations.

How many CVEs have patched wp_get_available_translations?: 2 published CVEs changed wp_get_available_translations in wordpress/core, in 1 distinct patches totalling 118 changed lines, between 2014 and 2014.
What is the latest CVE that changed wp_get_available_translations?: CVE-2014-5265, published 2014-08-18, changed lines 838 to 899 of trunk/wp-includes/l10n.php.
How does wp_get_available_translations compare to the rest of wordpress/core?: wordpress/core has 73 CVEs with a located fix in total; 2 of them changed wp_get_available_translations.
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