Skip to main content
Mallory
CriticalPublic exploitVulnerability

CVE-2023-39639: SQL Injection in LeoTheme leoblog <= 3.1.2 (LeoBlogBlog::getListBlogs)

Published Sep 14, 2023 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS9.8Critical · v3.1
EPSS0.81%57th percentile
CISA KEVNoNot listed
In the wildReported1 exploitation record in Mallory
Vendor
Leotheme
IdentifiersCVE-2023-39639CWE-89 · Improper Neutralization of Special…

A SQL injection vulnerability exists in LeoTheme leoblog up to version 3.1.2, specifically in the LeoBlogBlog::getListBlogs component. This vulnerability allows an attacker to manipulate SQL queries by injecting malicious input, potentially leading to unauthorized access or modification of database contents.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation of this vulnerability could allow an attacker to execute arbitrary SQL commands in the context of the application's database. This may result in data leakage, unauthorized data modification, or even full compromise of the underlying database.

Mitigation

If you can’t patch tonight, do this now.

As an interim measure, implement input validation and use parameterized queries in the LeoBlogBlog::getListBlogs component to prevent SQL injection. Restrict database permissions to minimize the impact of a successful attack.

Remediation

Patch, then assume compromise.

Upgrade LeoTheme leoblog to a version later than 3.1.2 where this vulnerability has been addressed. Ensure that all user-supplied input is properly sanitized and parameterized in SQL queries.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
LeothemeLeoblogapplication
FAQ

Frequently asked questions

Is CVE-2023-39639 exploited in the wild?
Yes. As of Oct 16, 2026, Mallory has reports of exploitation in the wild.
Is there a public exploit for CVE-2023-39639?
Yes. As of Oct 16, 2026, Mallory has reports of a public exploit for CVE-2023-39639.
Is there a patch for CVE-2023-39639?
Upgrade LeoTheme leoblog to a version later than 3.1.2 where this vulnerability has been addressed. Ensure that all user-supplied input is properly sanitized and parameterized in SQL queries.
What products are affected by CVE-2023-39639?
Leotheme Leoblog.
How severe is CVE-2023-39639?
CVE-2023-39639 has a CVSS v3.1 score of 9.8 (Critical) and an EPSS score of 0.81% (57th percentile) as of Oct 16, 2026.
Activity feed

Recent activity

1 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.

View more in app →

No news coverage yet. Advisories and community discussion only.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.