CVE-2024-7568: Pixeljar Favicon Generator cross-site request forgery (CSRF) (CVSS 9.6)

Description

The Favicon Generator plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 1.5. This is due to missing or incorrect nonce validation on the output_sub_admin_page_0 function. This makes it possible for unauthenticated attackers to delete arbitrary files on the server via a forged request granted they can trick a site administrator into performing an action such as clicking on a link. The plugin author deleted the functionality of the plugin to patch this issue and close the plugin, we recommend seeking an alternative to this plugin. CVE-2024-7864 appears to be a duplicate of this issue.

CVSS 3.1 breakdown

Attack vectorNetwork

Attack complexityLow

Privileges requiredNone

User interactionRequired

ScopeChanged

ConfidentialityHigh

IntegrityHigh

AvailabilityHigh

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H

Affected products

Pixeljar Favicon Generator< 2.1

Remediation

Fixed in

Pixeljar Favicon Generator≥ 2.1

Patch & vendor advisories

https://plugins.trac.wordpress.org/changeset?sfp_email=&sfph_mail=&reponame=&old=3139340%40favicon-generator&new=3139340%40favicon-generator&sfp_email=&sfph_mail=

References

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

Frequently asked

Is CVE-2024-7568 being actively exploited?

CVE-2024-7568 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.27%.

How severe is CVE-2024-7568?

CVE-2024-7568 has a CVSS 3.1 base score of 9.6, rated critical. EPSS estimates a 0.27% probability of exploitation.

Which products are affected by CVE-2024-7568?

Affected products include Pixeljar Favicon Generator.

How do I fix CVE-2024-7568?

Upgrade affected software to a fixed version, for example Pixeljar Favicon Generator 2.1 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2024-7568 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation works Book a demo