WordPress WP Mega Menu plugin <= 1.4.2 - PHP Object Injection vulnerability

published 2024-12-13 last yr. modified 2026-06-17 4mo ago also EUVD-2024-52406

cvss: 7.2; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.8%; EPSS 0.8% chance of exploitation in 30 days, percentile 58%
public exploits: 0; none known

Deserialization of Untrusted Data vulnerability in Themeum WP Mega Menu wp-megamenu allows Object Injection.This issue affects WP Mega Menu: from n/a through <= 1.4.2.

Is CVE-2024-54282 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation: none
Automatable: no
Technical impact: total
Assessed: last yr. (2024-12-13)

Exploit prediction

0.83% chance of exploitation in the next 30 days, higher than 58% of all scored CVEs (FIRST EPSS, 2026-11-11).

CVSS scores

assigned by	version	score	vector
CNA	3.1	7.2	CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

Affected products

Themeum WP Mega Menu

Classification

Weakness

CWE-502 Deserialization of Untrusted Data

Technology feeds

WordPress rss critical rss

References

patchstack.com /database/Wordpress/Plugin/wp-megamenu/vulnerability/wordpress-wp-mega-menu-plugin-1-4-2-php-object-injection-
vdb-entry

Sources

CVE List CVE-2024-54282
NVD CVE-2024-54282

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.