# CVE-2026-34788: Emlog SQL injection in tag_model updateTagName

Source: https://junglewise.ai/threats/cve-2026-34788-emlog-sql-injection-in-tag-model-updatetagname  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-04-03. Updated: 2026-07-25  
License: CC BY 4.0 with a link back

CVE-2026-34788 · Severity: medium · CVSS 6.5 · Published 2026-04-03

Emlog is an open-source website building and content management system. A security flaw in the tag management system allows an administrative user to execute unauthorized database commands. This could lead to the theft of sensitive information or the modification of website content, though it requires high-level access to exploit.

Technologies: [Emlog](https://junglewise.ai/threats/technologies/emlog). Vendors: [Emlog](https://junglewise.ai/threats/vendors/emlog).

## Quick answers

**Is CVE-2026-34788 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-34788 being exploited in the wild.

**How severe is CVE-2026-34788?** Medium severity, with a CVSS score of 6.5, published 3 April 2026.

**Which products and versions are affected?** Emlog <= 2.6.2.

**Is there a fix for CVE-2026-34788?** No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

**How is CVE-2026-34788 attacked?** It is attacked over the network, in a web application.

**Am I affected by CVE-2026-34788?** Check whether you run Emlog at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

A SQL injection vulnerability exists in the updateTagName() function within include/model/tag_model.php. The root cause is the direct interpolation of user-supplied variables ($tagName, $kw, $title, and $description) into a SQL UPDATE statement without proper escaping or parameterized queries. While the application uses addslashes(), this is insufficient to prevent injection in certain database configurations. An authenticated attacker with administrative privileges can exploit this via a network request to modify tag data, potentially gaining full read/write access to the database. As of the advisory date, no official patch has been released.

## Affected products

- Emlog Emlog <= 2.6.2

## Timeline

- 2026-03-31: advisory: GitHub Security Advisory published
- 2026-04-03: disclosed: NVD publication date

## References

- [https://github.com/emlog/emlog/security/advisories/GHSA-32mg-33qq-p3gf](https://github.com/emlog/emlog/security/advisories/GHSA-32mg-33qq-p3gf)

## Related threats

- [Emlog stored XSS in tag names via article editor](https://junglewise.ai/threats/cve-2026-73848-emlog-stored-xss-in-tag-names-via-article-editor)
- [Emlog stored XSS in Markdown article rendering](https://junglewise.ai/threats/cve-2026-53758-emlog-stored-xss-in-markdown-article-rendering)
- [Emlog path traversal in ZIP extraction enables RCE](https://junglewise.ai/threats/cve-2026-53757-emlog-path-traversal-in-zip-extraction-enables-rce)
- [Emlog SQL injection in queryDatabase function](https://junglewise.ai/threats/cve-2026-73850-emlog-sql-injection-in-querydatabase-function)
- [Emlog unauthenticated installation in install.php](https://junglewise.ai/threats/cve-2026-73849-emlog-unauthenticated-installation-in-install-php)