How many CVEs have patched getLogoSrc?

1 published CVEs changed getLogoSrc in OpenMage/magento-lts, in 1 distinct patches totalling 4 changed lines, between 2024 and 2024.

What is the latest CVE that changed getLogoSrc?

CVE-2024-41676 (Magento LTS vulnerable to stored Cross-site Scripting (XSS) in admin system configs), published 2024-07-29, changed lines 60 to 62 of app/code/core/Mage/Page/Block/Html/Header.php.

How does getLogoSrc compare to the rest of OpenMage/magento-lts?

OpenMage/magento-lts has 16 CVEs with a located fix in total; 1 of them changed getLogoSrc.

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

OpenMage/magento-lts

Function

getLogoSrc

Name: getLogoSrc in OpenMage/magento-lts: CVE fixes
Creator: RadicalNotion.AI
License: https://creativecommons.org/licenses/by-nc/4.0/

app/code/core/Mage/Page/Block/Html/Header.php

Last patched July 29, 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

getLogoSrc in OpenMage/magento-lts was changed by 1 published CVE fixes in 2024, in 1 distinct patches that added or removed 4 lines in total.

OpenMage/magento-lts has 16 CVEs with a located fix in total, so 6% of them touched this function.

CVEs that patched it

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

Magento LTS vulnerable to stored Cross-site Scripting (XSS) in admin system configs
CVE-2024-41676 · lines 60–62 · +3 −1
Medium · CVSS 5.1
EPSS 0.4%2024-07-29

Get an alert when the next CVE fix lands in OpenMage/magento-lts, with the patched functions.

Monitor magento-lts CVEs

Other functions in these files

Functions in the same file that CVE fixes also changed.

Other hotspots in the repository

Functions in OpenMage/magento-lts changed by the most CVE fixes.

validateAgainstBlockMethodBlacklist2 CVEs · app/code/core/Mage/Core/Helper/Security.php _generateAction2 CVEs · app/code/core/Mage/Core/Model/Layout.php _beforeSave1 CVEs · app/code/core/Mage/Sales/Model/Order.php loadValidOrder1 CVEs · app/code/core/Mage/Sales/Helper/Guest.php isRateLimitExceeded1 CVEs · app/code/core/Mage/Core/Helper/Data.php helper1 CVEs · app/code/core/Mage/Adminhtml/Block/Notification/Grid/Renderer/Actions.php

All patched functions in OpenMage/magento-lts

Frequently asked questions

Common questions about CVE fixes to getLogoSrc.

How many CVEs have patched getLogoSrc?: 1 published CVEs changed getLogoSrc in OpenMage/magento-lts, in 1 distinct patches totalling 4 changed lines, between 2024 and 2024.
What is the latest CVE that changed getLogoSrc?: CVE-2024-41676 (Magento LTS vulnerable to stored Cross-site Scripting (XSS) in admin system configs), published 2024-07-29, changed lines 60 to 62 of app/code/core/Mage/Page/Block/Html/Header.php.
How does getLogoSrc compare to the rest of OpenMage/magento-lts?: OpenMage/magento-lts has 16 CVEs with a located fix in total; 1 of them changed getLogoSrc.
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 OpenMage/magento-lts 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