CVE-2025-5095 is an authentication flaw in Burk Technology ARC Solo affecting the device's password change mechanism. A password change request can be sent directly to the device's HTTP endpoint without supplying valid credentials. The application fails to enforce proper authentication and session validation before processing the password update, allowing an unauthenticated requester to change credentials and take control of the device.
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.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository provides a proof-of-concept exploit for Burk Technology ARC Solo devices running firmware versions older than 1.0.60. The exploit consists of a Python Flask application (app.py) that emulates the device's web interface and API endpoints, along with HTML/JavaScript files (login.htm, post.json) that mimic the device's login and password change pages. The README.md provides step-by-step instructions: the attacker downloads the victim's post.json file, configures the local environment, and uses the provided web interface to change the admin password by sending crafted POST requests to the /post.json endpoint. The exploit leverages the device's insecure handling of password changes and configuration saving, allowing an attacker to reset the admin password and gain access. The main attack vector is network-based, targeting the device's web interface. The repository is structured with clear separation between the backend (Flask app) and frontend (HTML/JS), and is intended for demonstration and testing of the vulnerability.
8 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.