How many CVEs have patched get_translations_for_domain?

1 published CVEs changed get_translations_for_domain in wordpress/core, in 1 distinct patches totalling 54 changed lines, between 2016 and 2016.

What is the latest CVE that changed get_translations_for_domain?

CVE-2016-4566, published 2016-05-22, changed lines 786 to 851 of trunk/wp-includes/l10n.php.

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

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

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_translations_for_domain

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

trunk/wp-includes/l10n.php

Last patched May 22, 2016

1

CVEs

That changed this function

1

Distinct patches

Backports counted once

54

Lines changed

Added plus removed

2016

Years

By CVE publication date

Overview

get_translations_for_domain in wordpress/core was changed by 1 published CVE fixes in 2016, in 1 distinct patches that added or removed 54 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_translations_for_domain, newest first, with the lines each fix touched.

CVE-2016-4566
CVE-2016-4566 · lines 786–851 · +53 −1 in 2 hunks
Medium · CVSS 6.1
EPSS 6.0%2016-05-22

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

How many CVEs have patched get_translations_for_domain?: 1 published CVEs changed get_translations_for_domain in wordpress/core, in 1 distinct patches totalling 54 changed lines, between 2016 and 2016.
What is the latest CVE that changed get_translations_for_domain?: CVE-2016-4566, published 2016-05-22, changed lines 786 to 851 of trunk/wp-includes/l10n.php.
How does get_translations_for_domain compare to the rest of wordpress/core?: wordpress/core has 73 CVEs with a located fix in total; 1 of them changed get_translations_for_domain.
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