CVE-2026-54543Network attack vector

Authenticated DNS record injection via zone serialization

Published Aug 18, 2026 · Updated Aug 19, 2026

Injection in Froxlor before 2.3.8 allows remote authenticated users to add unauthorized DNS records through the DomainZones.add API. In lib/Froxlor/Api/Commands/DomainZones.php, DomainZones.add normalized record and type values but did not reject line breaks, tabs, semicolons, or unsupported RR types before lib/Froxlor/Dns/DnsEntry.php serialized them into a BIND zone-file line. An authenticated customer with DNS-zone permissions can therefore smuggle extra resource-record lines into a zone they are allowed to manage, causing DNS data integrity loss and possible zone-level resolution disruption.

CVSS severity5.4
Medium
EPSS probability0.43%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Injection in Froxlor before 2.3.8 allows remote authenticated users to add unauthorized DNS records through the DomainZones.add API. In lib/Froxlor/Api/Commands/DomainZones.php, DomainZones.add normalized record and type values but did not reject line breaks, tabs, semicolons, or unsupported RR types before lib/Froxlor/Dns/DnsEntry.php serialized them into a BIND zone-file line. An authenticated customer with DNS-zone permissions can therefore smuggle extra resource-record lines into a zone they are allowed to manage, causing DNS data integrity loss and possible zone-level resolution disruption.

The record

CVE
CVE-2026-54543
Published
Aug 18, 2026
Updated
Aug 19, 2026
Vendor
Froxlor
Product
Froxlor
Classifications
CWE-74, T1565.001
Attack vector
network
Privileges
authenticated

Timeline

How it unfolded

  1. Aug 18, 2026CVE publishedPublication date reported by the CVE source.
  2. Aug 19, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=< 2.3.8

What conditions does exploitation require?

Attack vectornetwork
Required privilegesauthenticated

What is affected?

Froxlor · Froxlorversion=< 2.3.8

Published CVSS scores

5.4GitHub_MCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 9, 2026Sep 15, 2026
Latest reporting daySep 15, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-74Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')
T1565.001Stored Data Manipulation

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo