Loading story…
OWASP's API Security Top 10 identifies broken object-level and function-level authorization, excessive data exposure, security misconfiguration, and unsafe trust boundaries as leading API risks, warning that business logic abuse and operational gaps often turn ordinary endpoints into high-impact exposures. Those patterns were reflected in newly disclosed incidents involving both enterprise software and consumer-facing platforms, where low-privileged access was enough to reach data and functions intended for administrators or other users.
In CVE-2026-46515, Frogman versions before 1.6.3 allowed users with only PERM_READ privileges to access administrative PBX data through MCP and HTTP APIs, including AMI manager secrets, outbound dial PINs, SIP secrets, backup paths, CDR history, and even root SSH connection commands; the flaw also enabled arbitrary execution of saved GraphQL queries and was rated CVSS 9.3. Separately, a bug bounty report on Target's Academy platform showed how two seemingly low-risk APIs could be chained to enumerate users and expose PII at scale, underscoring how weak authorization controls across interconnected endpoints can escalate routine API functionality into serious data disclosure.
Mallory correlates global threat intelligence with your attack surface — know if you’re exposed before adversaries strike.
5 events from the most recent confirmed update back to the earliest known activity.
The researcher said the Target Academy API finding resulted in a $2,000 bug bounty payout.
A bug bounty write-up described how two Target Academy API endpoints could be chained by a low-privileged user to enumerate users and expose sensitive PII at scale, resulting in a Broken Access Control finding.
The CVE advisory states that Frogman version 1.6.3 fixes the authorization flaw that exposed admin-grade data and enabled arbitrary saved GraphQL execution to low-privileged users.
A critical missing-authorization vulnerability affecting Frogman versions before 1.6.3 was disclosed, showing that PERM_READ users could access sensitive administrative data and execute saved GraphQL queries. The issue was rated CVSS 9.3 and described as remotely exploitable.
OWASP released its 2023 API Security Top 10, outlining major API risk categories including authorization failures, authentication weaknesses, SSRF, misconfiguration, inventory gaps, and insecure trust in third-party APIs.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
4 references tracked. Mallory keeps watching after this page renders.
meetcyber.net
Open sourceinfosecwriteups.com
Open sourcecvefeed.io
Open sourceowasp.org
Open sourceMap indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
Security researchers uncovered significant vulnerabilities in web applications due to broken access control mechanisms, leading to unauthorized privilege escalation and potential system compromise. In one case, a researcher discovered that a SaaS platform inadvertently exposed administrative functionalities to regular users. By simply signing up for a free trial, the user noticed an admin panel link was visible, which should not have been accessible to non-privileged accounts. Initial attempts to access the admin panel resulted in a 403 Forbidden error, but further probing revealed that the access control checks were insufficiently enforced. Through a series of advanced techniques, the researcher was able to escalate privileges, ultimately gaining access to sensitive administrative features and potentially compromising the entire system. This highlights the critical risk posed by misconfigured or broken permission models in enterprise SaaS environments, where a single oversight can grant attackers broad access to internal resources. In a separate incident, a security tester examining a hospital website identified two PHP endpoints protected by 403 Forbidden responses. Despite the initial access denial, the tester experimented with different HTTP methods and payloads, eventually bypassing the restriction by switching from a GET to a POST request and supplying the required form data. The server processed the request as if it were legitimate, exposing a workflow flaw that could allow unauthorized users to submit sensitive information or interact with backend systems. The tester replicated this technique on another endpoint, confirming that the access control logic was consistently weak across multiple parts of the application. Both incidents underscore the prevalence of insecure direct object references and improper authorization checks in modern web applications. Attackers can exploit these weaknesses to move laterally within systems, access confidential data, or disrupt critical workflows. The findings demonstrate the importance of rigorous access control validation, including proper segregation of user roles and comprehensive testing of all endpoints for privilege escalation vectors. Organizations are urged to review their authentication and authorization mechanisms, implement least privilege principles, and conduct regular security assessments to identify and remediate such vulnerabilities before they can be exploited. These real-world examples serve as a cautionary tale for developers and security teams, emphasizing that even seemingly minor oversights in access control can have far-reaching consequences for data security and operational integrity.
Jul 12, 2026
Security researchers reported a **critical Moltbook** exposure caused by an unauthenticated database/API access issue that allowed enumeration of agent records (e.g., `GET /api/agents/{id}`) and leakage of **email addresses, JWT `login_token`s, and third-party `api_key`s**, enabling agent hijacking and downstream abuse of connected services. Separately, **Cal.com Cloud** was found vulnerable to a chained set of broken access controls and signup/invite-token logic flaws that enabled **complete account takeover** and access to sensitive booking data (attendee details, emails, and booking histories) at scale, including organizational accounts. In parallel, SentinelLabs documented that roughly **175,000 internet-exposed Ollama** instances were reachable due to common deployment misconfiguration (binding to `0.0.0.0`/public interfaces), creating conditions for **arbitrary code execution** and access to external resources—especially where tool-calling features were enabled. A distinct IoT case study described **Molekule** air purifiers exposing fleet-wide telemetry because an **AWS Cognito Identity Pool** permitted unauthenticated access to **AWS IoT Core MQTT** subscriptions, leaking device shadow data (e.g., Wi‑Fi SSIDs, MAC addresses, device names, sensor readings) for ~100,000 devices; the disclosed policy reportedly allowed read/subscribe access but not device control without per-device certificates.
Jun 29, 2026
FreePBX, the open-source IP PBX platform, has patched several critical vulnerabilities in its Endpoint Manager module that could allow attackers to bypass authentication and achieve remote code execution. Researchers from Horizon3.ai identified three high-severity flaws: CVE-2025-66039 (authentication bypass via forged Basic Auth headers when 'webserver' authorization is enabled), CVE-2025-61675 (multiple SQL injection vulnerabilities across several endpoints), and CVE-2025-61678 (arbitrary file upload enabling PHP webshell deployment). These vulnerabilities, when chained, allow unauthenticated attackers to gain full control over affected FreePBX instances, posing a significant risk to business communications infrastructure. The authentication bypass is not present in the default configuration but becomes exploitable if certain advanced settings are enabled. Attackers can exploit these flaws to access protected endpoints, manipulate the underlying SQL database, and upload malicious files for command execution. The vulnerabilities were responsibly disclosed to FreePBX maintainers, and patches have been released. Organizations using FreePBX, especially those with non-default authentication settings, are urged to update immediately to mitigate the risk of compromise.
Jun 29, 2026