LiveActive security incident?Get immediate response
CVE Record

CVE-2024-13010: WP Foodbakery <= 4.8 - Reflected Cross-Site Scripting

The WP Foodbakery plugin for WordPress is vulnerable to Reflected Cross-Site Scripting in versions up to, and including, 4.8 due to insufficient input sanitization and output escaping on the 'search_type' parameter. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link.

MediumCVSS 6.1Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2024-13010 affects the WP Foodbakery WordPress plugin through version 4.8. A malicious link can cause script to run in a victim's browser if clicked. This is mainly a phishing/session-risk issue, not a direct server takeover in the provided sources.

Executive priority

Treat as a scheduled remediation item, with higher urgency for public WordPress sites used by administrators or customers. Prioritize inventory first because exposure depends on plugin presence and version.

Technical view

The issue is reflected cross-site scripting caused by insufficient sanitization and output escaping of the search_type parameter. It is unauthenticated, network-reachable, and low complexity, but requires user interaction. CVSS is 6.1 under CVSS 3.1, mapped to CWE-79.

Likely exposure

Exposure is likely limited to WordPress sites running WP Foodbakery version 4.8 or earlier, especially sites where users or administrators may follow crafted external links.

Exploitation context

The source bundle does not show CISA KEV listing or cited evidence of active exploitation. Successful abuse requires tricking a user into taking an action such as clicking a crafted link.

Researcher notes

Evidence supports reflected XSS in search_type for WP Foodbakery through 4.8. Provided sources do not establish active exploitation, a KEV listing, or a specific fixed version. Avoid assuming broader theme or WordPress core impact.

Mitigation direction

  • Inventory WordPress sites for WP Foodbakery and record installed versions.
  • Check vendor, marketplace, and Wordfence guidance for a fixed release or official mitigation.
  • Update WP Foodbakery if a fixed version is available from the vendor.
  • Disable or remove the plugin where it is unnecessary or cannot be remediated promptly.
  • Warn administrators against following unsolicited links to affected site pages.

Validation and detection

  • Confirm whether WP Foodbakery is installed on each WordPress site.
  • Verify whether installed versions are 4.8 or earlier.
  • Review web logs for unusual search_type parameter activity without reproducing payloads.
  • Confirm the plugin is updated, disabled, or removed after remediation decisions.
  • Retest affected pages for safe output encoding using approved internal testing procedures.
Prepared
Confidence
medium
Sources
4

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-79: 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-13010 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
6.1 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/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
3Source 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
6.1CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N2.82.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/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
ChimpstudioWP Foodbakery0unaffected
Weakness

CWE details

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

CWE-79 · source CWE mapping

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.