LiveActive security incident?Get immediate response
CVE Record

CVE-2024-51606: WordPress Blrt WP Embed plugin <= 1.6.9 - SQL Injection vulnerability

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Blrt Blrt WP Embed blrt-wp-embed allows SQL Injection.This issue affects Blrt WP Embed: from n/a through <= 1.6.9.

HighCVSS 8.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2024-51606 is a high-severity SQL injection issue in the WordPress Blrt WP Embed plugin through version 1.6.9. A low-privileged authenticated user may be able to make the plugin interact unsafely with the database, creating risk of sensitive data exposure and some service impact.

Executive priority

Prioritize within normal high-severity patch windows, faster for public WordPress sites with many user accounts. The main business concern is potential database confidentiality exposure from a plugin-level flaw.

Technical view

The record maps to CWE-89 with CVSS 3.1 score 8.5: network exploitable, low complexity, low privileges required, no user interaction, changed scope, high confidentiality impact, no integrity impact, and low availability impact. The provided sources do not identify the vulnerable parameter, endpoint, proof of concept, or a fixed version.

Likely exposure

Exposure is limited to WordPress sites with the Blrt WP Embed plugin installed at version 1.6.9 or earlier. The CVSS privileges-required value suggests unauthenticated internet users are not enough; a low-privileged WordPress account may be required.

Exploitation context

The source bundle does not show CISA KEV listing or any cited evidence of active exploitation. Treat this as a serious authenticated SQL injection risk, but do not claim exploitation in the wild from the available evidence.

Researcher notes

Evidence is limited to the CVE and Patchstack entry. Key missing details include vulnerable code path, required WordPress role, exploit preconditions, public exploit availability, and fixed release. Avoid assumptions beyond the CVSS vector and affected version range.

Mitigation direction

  • Inventory WordPress sites for the blrt-wp-embed plugin and installed version.
  • Check Patchstack and vendor guidance for a fixed version or official workaround.
  • Disable or remove the plugin where business impact allows until remediation is confirmed.
  • Limit and review low-privileged WordPress accounts while the plugin remains installed.
  • Back up the site and database before applying any vendor-recommended change.

Validation and detection

  • Confirm whether blrt-wp-embed is installed and whether the version is 1.6.9 or earlier.
  • Review administrator, author, contributor, and subscriber accounts for unnecessary access.
  • Check web and application logs for unusual plugin requests or database error patterns.
  • Verify any remediation against current Patchstack or vendor advisory details.
  • Document affected sites, remediation status, and remaining accepted risk.
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-89: Database access and collection lookup

Injection into data stores can inform collection, data access, and exfiltration detection reviews. 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
description · low confidence lookup

Database behavior lookup

The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2024-51606 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
High
CVSS
8.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/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
3Timeline events
1ADP providers
2Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

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
8.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:L3.14.7Patchstack

Vulnerability scoring details

Base CVSS 3.1 score

8.5High
CVSS 3.1 vector shape for CVE-2024-51606Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/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

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
BlrtBlrt WP Embedblrt-wp-embed, 0unaffected
Weakness

CWE details

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

CWE-89 · source CWE mapping

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.