CVE-2025-66390 describes a cross-tenant self-service signup logic flaw in Microsoft Azure API Management, observed through 2025-10-17. When username/password Basic Authentication self-service signup is enabled in one tenant, an attacker can reuse the registration flow against a different tenant by modifying the hostname or tenant identifier in the request. As a result, a tenant that has signup disabled in the user interface may still accept signup requests because the underlying API endpoint remains reachable and processes cross-tenant requests based on the Host header. The reported issue is therefore a mismatch between UI-level configuration state and backend enforcement of the signup workflow. The supplier assessed the behavior as not crossing a security boundary and characterized it as a configuration or state-management issue rather than a tenant-isolation vulnerability.
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 is a small, focused proof-of-concept for abusing Azure API Management developer portal signup when the frontend self-service registration UI is disabled but backend registration endpoints remain exposed. It contains two files: a README describing the vulnerability and post-signup attack chain, and a single Python script, apim_signup.py, which is the exploit entry point. The Python script is interactive and operational rather than a mere detector. It prompts the operator for a target APIM developer portal URL, email, first name, last name, password, and optional HTTP proxy. It then performs three core actions: (1) GETs /v2/captcha-challenge from the target, (2) brute-forces the SHA-256 proof-of-work solution by iterating from 0 to maxnumber and comparing SHA-256(salt+n) to the returned challenge, and (3) POSTs the solved challenge and attacker-controlled signup data to /signup. TLS verification is explicitly disabled, and the script supports routing traffic through a local interception proxy such as Burp or Caido. The exploit capability is account creation on the APIM developer portal despite disabled signup in the UI. The README further documents a likely follow-on path after successful registration: confirm the email, authenticate to the APIM management API with Basic auth, retrieve the internal user ID, self-subscribe to the default Starter product, list subscription secrets, and then call backend APIs through the APIM gateway using the issued subscription key. Those later steps are not automated in the Python script, but they clearly describe the intended impact of the initial signup bypass. There is no evidence this repository belongs to a common exploit framework such as Metasploit or Nuclei. The code is straightforward standalone Python using requests, hashlib, base64, json, time, getpass, and urllib3. Overall, this is a real exploit PoC targeting Microsoft Azure API Management misconfigurations related to exposed signup functionality, with a basic but functional payload that directly creates accounts rather than delivering shellcode or code execution.
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.
1 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.