{"answers":{"affected":"2 open source packages ship an affected version, including froxlor/froxlor.","exploited":"There is no known exploitation of CVE-2026-54543 in the wild and no public exploit code.","fix":"Upgrade froxlor/froxlor to 2.3.8 or later.","what":"CVE-2026-54543 is a medium-severity vulnerability in froxlor, published on 18 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-54543 and fix it if it is affected.\n\nWhat it is: CVE-2026-54543 is a medium-severity vulnerability in froxlor, published on 18 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-54543 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- froxlor/froxlor (Packagist): affected all versions; fixed in 2.3.8\n- froxlor/froxlor (Packagist): affected all versions; fixed in 2.3.8\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-54543/ (Markdown: https://insights.sbomify.com/CVE-2026-54543/index.md)","id":"CVE-2026-54543","markdown":"https://insights.sbomify.com/CVE-2026-54543/index.md","name":"CVE-2026-54543","record":{"aliases":["GHSA-5rw4-4665-cvwf"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_modify","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Server administration software","requires_auth":"low_privilege","summary":"Authenticated users can inject malicious DNS records into zone files via the DomainZones.add API, allowing unauthorized DNS data modification and potential service disruption.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":5.4,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-74","name":"Improper Neutralization of Special Elements in Output Used by a Downstream Component"}],"description":"Froxlor is open source server administration software. Prior to 2.3.8, the DomainZones.add API command in lib/Froxlor/Api/Commands/DomainZones.php accepts user-controlled record and type values without rejecting line delimiters, tab characters, semicolons, or unsupported DNS record types before lib/Froxlor/Dns/DnsEntry.php serializes the values into a BIND zone file. An authenticated customer with DNS-zone permissions can place a crafted value in the record field, or use the related type-field variant, to create additional resource-record lines that bypass Froxlor's field-level validation. BIND accepts the injected records, allowing modification of DNS data and possible DNS availability impact within a zone the caller is authorized to manage. This issue is fixed in version 2.3.8.","ecosystems":["Packagist"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Froxlor DomainZones.add allows DNS zone-file RR injection via record/type fields","id":"CVE-2026-54543","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"other","year":"2026"},"n_packages":2,"n_references":3,"next":{"headline":"Fireshare has unauthenticated SSRF via missing login_required on webhook test endpoints","id":"CVE-2026-54544"},"packages":[{"ecosystem":"Packagist","fixed":["2.3.8"],"introduced":["0"],"last_affected":[],"package":"froxlor/froxlor","purl":null,"source":"GHSA-5rw4-4665-cvwf"},{"ecosystem":"Packagist","fixed":["2.3.8"],"introduced":["0"],"last_affected":[],"package":"froxlor/froxlor","purl":"pkg:composer/froxlor/froxlor","source":"GHSA-5rw4-4665-cvwf"}],"prev":{"headline":"Nimiq: Out-of-bounds panic in KeyNibbles::Add from oversized child suffix in a deserialized proof","id":"CVE-2026-54542"},"products":["froxlor"],"published":"2026-08-18","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-19","vendors":["froxlor"]},"summary":"Authenticated users can inject malicious DNS records into zone files via the DomainZones.add API, allowing unauthorized DNS data modification and potential service disruption.","url":"https://insights.sbomify.com/CVE-2026-54543/"}