LiveActive security incident?Get immediate response
CVE Record

CVE-2024-13701: Liveticker (by stklcode) <= 1.2.2 - Authenticated (Contributor+) Stored Cross-Site Scripting

The Liveticker (by stklcode) plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's 'liveticker' shortcode in all versions up to, and including, 1.2.2 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

CVE-2024-13701 is a stored cross-site scripting issue in the Liveticker WordPress plugin. A logged-in user with Contributor-level access or higher could place script content through the plugin shortcode, causing it to run when someone views the affected page.

Executive priority

Treat as a moderate-priority WordPress hygiene issue. It is not reported as actively exploited here, but sites with many content contributors should prioritize review and vendor-confirmed updates.

Technical view

The vulnerability is CWE-79 stored XSS in Liveticker by stklcode through the `liveticker` shortcode. Sources attribute it to insufficient sanitization and output escaping of user-supplied shortcode attributes in versions up to and including 1.2.2. CVSS 3.1 is 6.4 with low complexity and low privileges required.

Likely exposure

Exposure is most likely on WordPress sites running Liveticker versions up to 1.2.2, especially where Contributor or higher accounts are numerous, shared, or weakly controlled.

Exploitation context

The bundle does not show CISA KEV listing or cited active exploitation. Abuse requires authenticated Contributor-level access or higher, but successful stored XSS can affect later page viewers, including privileged users.

Researcher notes

Evidence names the vulnerable path as shortcode attribute handling. The provided bundle does not name a fixed version, despite including a WordPress changeset reference. Avoid assuming patch status without vendor confirmation.

Mitigation direction

  • Inventory WordPress sites for Liveticker by stklcode and plugin version.
  • Check vendor or WordPress plugin guidance for a fixed release before updating.
  • Restrict Contributor-level access to trusted users only.
  • Review published content using the `liveticker` shortcode.
  • Remove or revise suspicious shortcode attributes pending vendor guidance.

Validation and detection

  • Confirm whether Liveticker is installed and whether version is 1.2.2 or earlier.
  • Review roles with Contributor, Author, Editor, or Administrator privileges.
  • Inspect pages and posts containing the `liveticker` shortcode.
  • Use safe code review or scanning to confirm shortcode output escaping.
  • Check logs or content history for unexpected shortcode attribute changes.
Prepared
Confidence
high
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-13701 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
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.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-13701Attack 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
stklcodeLiveticker (by stklcode)0unaffected
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.