LiveActive security incident?Get immediate response
CVE Record

CVE-2024-12452: Ziggeo <= 3.1 - Authenticated (Contributor+) Stored Cross-Site Scripting

The Ziggeo plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's 'ziggeo_event' shortcode in all versions up to, and including, 3.1 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

MediumCVSS 6.4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

Ziggeo for WordPress through version 3.1 allows logged-in users with Contributor or higher privileges to store malicious script through the ziggeo_event shortcode. The script runs when someone views the affected page. This is not reported as actively exploited, but it can create account and site-administration risk if trusted users or compromised accounts can publish content.

Executive priority

Treat as a moderate-priority WordPress application risk. Prioritize sites with many content contributors, external authors, or elevated admin exposure, because stored XSS can affect users who only view compromised content.

Technical view

This is a stored cross-site scripting issue caused by insufficient sanitization and output escaping of shortcode attributes in Ziggeo's ziggeo_event handling. CVSS is 6.4 with low attack complexity and low privileges required. The impact is scoped to confidentiality and integrity, with no availability impact stated.

Likely exposure

Exposure is most likely on WordPress sites running Ziggeo versions up to and including 3.1, especially where Contributor-level users, guest authors, or compromised low-privilege accounts can create content using shortcodes.

Exploitation context

The source bundle does not cite CISA KEV listing or active exploitation. Exploitation requires authenticated Contributor-level access or higher, and the stored script executes when another user accesses the injected page.

Researcher notes

The CVE prose and Wordfence reference identify versions through 3.1 and the shortcode vector. The supplied affected-product metadata is sparse, and the bundle does not clearly name a fixed version, so remediation should be tied to vendor or WordPress plugin guidance.

Mitigation direction

  • Inventory WordPress sites using the Ziggeo plugin.
  • Check vendor and WordPress plugin guidance for a fixed release.
  • Upgrade Ziggeo if a patched version is available.
  • Restrict Contributor and author permissions until remediated.
  • Review content containing ziggeo_event shortcodes for unsafe attributes.

Validation and detection

  • Confirm installed Ziggeo versions across WordPress environments.
  • Identify pages or posts using the ziggeo_event shortcode.
  • Verify Contributor-level users cannot store unsafe shortcode attributes in staging.
  • Review the referenced WordPress Trac changeset for sanitization and escaping changes.
  • Check logs and content history for suspicious shortcode edits.
Prepared
Confidence
medium
Sources
5

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-12452 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.4 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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
4Source 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.4CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N3.12.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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
oliverfriedmannZiggeo0unaffected
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.