LiveActive security incident?Get immediate response
CVE Record

CVE-2024-24876: WordPress Admin Menu Editor Plugin <= 1.12 is vulnerable to Cross Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) vulnerability in Janis Elsts Admin Menu Editor.This issue affects Admin Menu Editor: from n/a through 1.12.

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This is a medium-severity CSRF issue in the WordPress Admin Menu Editor plugin through version 1.12. An attacker could trick a logged-in user into causing an unintended plugin-related action, affecting site integrity. The supplied sources do not show data theft, service outage, or confirmed exploitation.

Executive priority

Treat this as a routine but real WordPress integrity risk. It is not currently supported as actively exploited, but affected sites should be identified and remediated through normal patch management because exploitation could alter administrative behavior or settings.

Technical view

CVE-2024-24876 is CWE-352 in Janis Elsts Admin Menu Editor for WordPress, affecting versions through 1.12. CVSS 3.1 is 4.3 with network attack vector, low complexity, no attacker privileges, required user interaction, unchanged scope, low integrity impact, and no confidentiality or availability impact.

Likely exposure

Exposure is likely limited to WordPress sites running the Admin Menu Editor plugin at version 1.12 or earlier. Practical risk depends on whether privileged users are authenticated when interacting with attacker-controlled content and what plugin actions can be forged.

Exploitation context

CISA KEV is false, and the provided sources do not cite active exploitation. The attack class requires user interaction and typically depends on abusing an authenticated browser session. The available evidence supports integrity risk only, not direct disclosure or denial of service.

Researcher notes

The source bundle identifies the issue and CVSS vector but does not provide a vulnerable endpoint, exploit details, patch version, or concrete workaround. Validation should remain inventory- and vendor-guidance based unless additional primary evidence becomes available.

Mitigation direction

  • Inventory WordPress sites for Admin Menu Editor version 1.12 or earlier.
  • Check vendor, WordPress plugin, or Patchstack guidance for fixed versions or workarounds.
  • Upgrade, disable, or remove the plugin where vendor guidance indicates risk.
  • Reduce unnecessary administrator browsing while authenticated to WordPress.
  • Prioritize production sites where admin menu changes affect operations.

Validation and detection

  • Confirm whether the plugin package admin-menu-editor is installed.
  • Record the installed plugin version on each WordPress site.
  • Review plugin change logs or vendor notices for CSRF remediation guidance.
  • Check whether exposed sites have active administrator users.
  • Document compensating controls if no fixed version is confirmed.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-352: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2024-24876 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
4.3 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
4.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N2.81.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

4.3Medium
CVSS 3.1 vector shape for CVE-2024-24876Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Janis ElstsAdmin Menu Editoradmin-menu-editor, n/aunaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-352 · source CWE mapping

Cross-Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.