AITiny is a powerful content-generation and image-editing tool. A user with access to its features can prompt the configured AI service to fetch a remote URL — for example when submitting a reference image for image editing — and to include any content the AI returns in the editor or in saved Joomla articles. The same is true of any Joomla extension that lets editors embed externally-hosted images, including the Media Manager's filesystem providers and the media form field.
For these reasons the guidance in How user groups are handled is doubly important: access to AITiny features should be limited to a small number of trusted users, and you should monitor the use of your AI service closely with sensible spending limits applied.
Configuring an AI service — including a third-party Custom endpoint — requires core.edit on com_plugins. This is the same privilege that lets an administrator see and rotate the API key, so it should be granted only to people you would also trust with the key itself.
AITiny cannot defend against a hostile AI service. Once you have given an untrusted provider the endpoint URL and the API key, that provider can return any content it likes — including crafted content designed to take advantage of editor-side rendering bugs in AITiny or in third-party extensions, or content designed to manipulate editors into publishing misinformation on your behalf.
Only point AITiny at AI service providers you would be willing to hand your article contents and your API key to. Free or unknown providers, public proxies, and any endpoint you cannot identify the operator of should be treated as hostile.
When you submit a reference image URL for image generation or editing, AITiny has to fetch that URL server-side in order to send the bytes to the AI service. If the URL points at the site itself the file is read directly from the filesystem; otherwise it is fetched over HTTP(S). In every branch the response is validated as a supported image (PNG, JPEG, WebP, GIF, BMP), capped at 50 MB, and never echoed back to the editor.
This validation is what makes legitimate workflows — third party CDNs, placeholder services, and externally-hosted AI-generated images — work safely. It does not, however, eliminate the residual blind server-side request capability: a sufficiently motivated attacker with access to AITiny features could still point the fetch at an internal host whose response happens to be a valid image. The same caveat applies to any Joomla extension that lets editors embed images hosted on third party domains, including the Media Manager's filesystem providers and the media form field.
Please report security issues in AITiny to <[email protected]> rather than disclosing them publicly, so we can coordinate a fix and an advisory.