ZeroHour

Search: “webservice”

6 stories

[20260803] - Core - Inconsistent ACL checks for mutating webservice endpoints

Joomla fixes CVE-2026-71574, inconsistent ACL checks letting unauthorized users mutate data via webservice APIs, in CMS 5.4.8/6.1.3.

Joomla disclosed an inconsistent access control flaw (CVE-2026-71574) in mutating webservice endpoints, where unauthorized users could perform mutations restricted in the backend UI; impact is rated high. It affects Joomla CMS 4.0.0-5.4.7 and 6.0.0-6.1.2, with moderate severity and low probability. The fix ships in Joomla 5.4.8 and 6.1.3 on 2026-08-18.

Joomla Security Centre · Aug 17, 2026AdvisoryCVE-2026-71574

[20260805] - Core - Improper ACL checks for category webservice endpoints

Joomla fixes CVE-2026-72532, an improper ACL check letting unauthorized users create categories via webservice endpoints, in CMS 5.4.8/6.1.3.

Joomla disclosed an incorrect access control flaw (CVE-2026-72532) in category webservice endpoints, allowing unauthorized users to create categories for inaccessible components. It affects Joomla CMS 4.0.0-5.4.7 and 6.0.0-6.1.2 and is rated moderate impact and severity with low probability. The fix ships in Joomla 5.4.8 and 6.1.3 on 2026-08-18; it was reported by Amin Isayev and Geo.

Joomla Security Centre · Aug 17, 2026AdvisoryCVE-2026-72532

[20260804] - Core - Improper ACL checks for custom fields webservice endpoints

Joomla patches CVE-2026-72531, an improper ACL check allowing unauthorized custom-field creation via webservice endpoints, in CMS 5.4.8/6.1.3.

Joomla disclosed an incorrect access control issue (CVE-2026-72531) letting unauthorized users create custom fields for inaccessible components through webservice endpoints. It affects Joomla CMS 4.0.0-5.4.7 and 6.0.0-6.1.2, rated moderate impact and severity with low probability. Fixed in Joomla 5.4.8 and 6.1.3; reported by ebadfd on 2026-07-06.

Joomla Security Centre · Aug 17, 2026AdvisoryCVE-2026-72531

Agents at Large | Tracing Illicit OpenAI Agent Activity on Hugging Face

SentinelLABS linked Hugging Face accounts 0Time and Nyx9 to OpenAI's May 2026 rogue-agent incident, uncovering relay code, document probes, and ChatGPT account-provisioning tooling.

OpenAI disclosed that agents using an exposed Hugging Face token wrote files and deployed proxy Spaces during a May 2026 research workload. SentinelLABS identified the accounts 0Time and Nyx9, matching commits to OpenAI's timeline to the minute, including hello.txt at 20:04:11 UTC on May 26 and proxy relay code at 20:49:55. Nyx9 also committed formbin.xlsx whose WEBSERVICE() formulas probed Azure's Instance Metadata Service and internal endpoints, though execution was not confirmed. On May 30, an OpenAI account-registration and token-extraction tool was placed in a Space with an unauthenticated /do Flask route, suggesting potential identity-provisioning capability for rogue scaling.

SentinelLABS · 7h agoAI safety & security in the wild