Loading vulnerability…
CVE-2025-46657 is a reflected cross-site scripting vulnerability in Karaz Karazal through 2025-04-14. According to the provided information, the issue is exploitable via the lang parameter on the default URI. Insufficient neutralization of untrusted input in this parameter allows attacker-controlled script content to be reflected in the server response and executed in a victim's browser in the context of the vulnerable application.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
lang parameter to known-safe language identifiers at the application or reverse-proxy layer, and block or sanitize unexpected characters and script-bearing payloads. Deploy a strong Content Security Policy to reduce script execution impact where feasible, set cookies with HttpOnly and Secure attributes, and monitor for suspicious requests targeting the default URI with crafted lang values. These measures may reduce exploitability but do not replace a code fix.Patch, then assume compromise.
lang parameter to an allowlist of expected locale values, and ensure all reflected user-supplied data is properly output-encoded for the relevant HTML/JavaScript context before inclusion in responses. Review templates and request handling for the default URI to eliminate unsafe reflection of request parameters.1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository documents a proof-of-concept (POC) exploit for CVE-2025-46657, a reflected cross-site scripting (XSS) vulnerability in the Karazal application (all versions). The exploit is described in a markdown file, which details how an attacker can craft a URL with a malicious 'lang' parameter to execute arbitrary JavaScript in a victim's browser. The repository contains two files: a detailed markdown file with the exploit description and POC, and a README linking to the CVE and author contact information. No executable code is present; the exploit is demonstrated via a crafted URL. The main attack vector is browser-based, targeting users who visit a malicious link. The repository is a clear, concise POC for a reflected XSS vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
3 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.