LiveActive security incident?Get immediate response
CVE Record

CVE-2024-24871: WordPress Blocksy theme <= 2.0.19 - Cross Site Scripting (XSS) vulnerability

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in creativethemeshq Blocksy blocksy.This issue affects Blocksy: from n/a through <= 2.0.19.

MediumCVSS 6.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2024-24871 is a cross-site scripting issue in the WordPress Blocksy theme through version 2.0.19. If triggered, attacker-controlled script could run in a user’s browser. The CVSS data indicates a logged-in attacker role and user interaction are required, so urgency is moderate rather than emergency-level.

Executive priority

Treat this as a normal-priority web application remediation item. It is not listed as actively exploited, but affected public WordPress sites should be updated because XSS can support session abuse, content tampering, or phishing against site users.

Technical view

The vulnerability is CWE-79, improper neutralization of input during webpage generation, in creativethemeshq Blocksy. It is remotely reachable with low attack complexity, requires low privileges and user interaction, and has changed scope with limited confidentiality, integrity, and availability impact per CVSS 3.1 score 6.5.

Likely exposure

Exposure is limited to WordPress sites running the Blocksy theme at version 2.0.19 or earlier. The bundle does not identify affected configurations, vulnerable fields, or plugin dependencies, so validation should start with theme inventory and version checks.

Exploitation context

The source bundle does not report active exploitation, and CISA KEV status is false. CVSS indicates exploitation requires an authenticated low-privilege role and a victim interaction, reducing broad internet-scale risk but still relevant for multi-user WordPress sites.

Researcher notes

Available evidence identifies the product, affected version range, CWE, and CVSS vector, but not the vulnerable parameter, exact attack path, or fixed version. Avoid assuming exploit availability or patch details beyond the cited sources.

Mitigation direction

  • Inventory all WordPress sites using the Blocksy theme.
  • Update Blocksy beyond 2.0.19 after confirming vendor or Patchstack guidance.
  • Restrict low-privileged WordPress accounts until remediation is complete.
  • Review WordPress roles and remove unused contributor-level access.
  • Monitor vendor, CVE, and Patchstack entries for updated remediation details.

Validation and detection

  • Confirm whether Blocksy is installed on each WordPress site.
  • Record the installed Blocksy version and flag versions through 2.0.19.
  • Check whether vendor guidance identifies a fixed release.
  • Review recent content changes for unexpected script-like markup.
  • Confirm remediation by rechecking the theme version after update.
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-24871 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.5 (3.1)
Known Exploited
No
Published

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

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.5CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L2.33.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

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

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

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
creativethemeshqBlocksyblocksy, 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.