NVD / CVE Program· CNA GitHub_M

CVE-2026-34788: Emlog: SQL Injection in tag_model::updateTagName() via unsanitized parameters

Noroxi assessment

Priority: Monitor (action score 26/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.35% (FIRST EPSS).
Anyone who can reach it over the internet can trigger it. Administrator privileges are required. No user action is required. No special conditions are required; it is repeatable.
According to the record, no fixed version is available yet.

Low priority for now. Update when a fix is released; follow the vendor's advisory.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

Emlog is an open source website building system. In versions 2.6.2 and prior, a SQL injection vulnerability exists in include/model/tag_model.php at line 168. The updateTagName() function directly interpolates user input into the SQL query string without using parameterized queries or proper escaping ($this->db->escape_string()), making it vulnerable to SQL injection attacks. At time of publication, there are no publicly available patches.

MediumCVSS 6.5 · v3.1—No exploit No fix recorded

SQL injection

Published: Apr 3, 2026
Updated: Jul 24, 2026
EPSS: 0.3% · 29th percentile
CWE: CWE-89

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 26 / 40 · 6.5 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.3%

CISA SSVC decision

Exploitation: proof of concept
Automatable: no
Technical impact: total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: —
CNA · GitHub_M: 6.5; NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
No fixed version yet

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
emlog	emlog	cpe:2.3:a:emlog:emlog

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

emlog emlogup to 2.6.2 inclusive

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

emlog emlog
- <= 2.6.2affected

Same product

emlog: all records

Other highest-scoring records for the same primary product.

CVE-2023-44974An arbitrary file upload vulnerability in the component /admin/plugin.php of Emlog Pro v2.2.0 allows attackers to execute arbitrary code via
45Plan
CVE-2026-42287Emlog: SQL Injection Vulnerability in log_model.php within addLog() and updateLog() Functions
40Plan
CVE-2023-43291Deserialization of Untrusted Data in emlog pro v.2.1.15 and earlier allows a remote attacker to execute arbitrary code via the cache.php com
40Plan

Published before and after this one in the same product

← EarlierCVE-2026-34607Apr 3, 2026 · Emlog: Path Traversal in emUnZip() allows arbitrary file write leading to RCE
28Monitor
← EarlierCVE-2026-34787Apr 3, 2026 · Emlog: Local File Inclusion in plugin.php via unsanitized plugin parameter
26Monitor
Later →CVE-2026-41517May 8, 2026 · Emlog: Remote Code Execution via Malicious Plugin Upload
0Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

No fix version is recorded for this entry. Check the references for vendor advisories.

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

CVE-2026-4228735 days apartEmlog: SQL Injection Vulnerability in log_model.php within addLog() and updateLog() Functions
40Plan
CVE-2025-47785323 days apartEMLOG SQL Injection Vulnerability
35Monitor
CVE-2026-73850133 days apartEmlog: Arbitrary SQL Execution Vulnerability in ai.php within queryDatabase() Function
34Monitor
CVE-2025-30372371 days apartEmlog Pro contains an SQL injection vulnerability.
30Monitor
CVE-2026-53756154 days apartEmlog Blind SQL Injection via Authentication Cookie
19Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

CVE-2025-62717161 days apartEmlog Pro session verification code error due to clearing logic error
10Monitor

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

Anyone who can reach it over the internet can trigger it.
Administrator privileges are required.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: high · data can be read
Integrity: high · data or configuration can be modified
Availability: none

Attack vector: Network
Attack complexity: Low
Privileges required: High
User interaction: None
Scope: Unchanged
Confidentiality impact: High
Integrity impact: High
Availability impact: None

Weakness class (CWE)

CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N

nvd-secondary

Root cause

The query text is built by concatenating user input. The database cannot tell where the data ends and the command begins.

The bug in code

The whole CWE-89 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1const owner = req.query.owner;
2const rows = await db.query(
3  "SELECT * FROM files WHERE owner = '" + owner + "'"
4);

Fixed

1const owner = req.query.owner;
2const rows = await db.query(
3  "SELECT * FROM files WHERE owner = $1",
4  [owner]
5);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Attack patterns (CAPEC)

ATT&CK techniques

—

Change log

No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.

All records