# CVE-2026-102777: Server-side request forgery in Event Gallery for Joomla

> An attacker can exploit SSRF in the Google Photos picker to leak OAuth tokens or access internal networks via a logged-in administrator session.

- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:L/VI:N/VA:N/SC:H/SI:L/SA:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 5 Oct 2026
- **Updated:** 6 Oct 2026
- **Also known as:** GHSA-2gw6-8g27-32rm

## What is CVE-2026-102777?

CVE-2026-102777 is a medium-severity server-side request forgery vulnerability in svenbluege.de Event Gallery for Joomla, published on 5 Oct 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Joomla Extension - svenbluege.de - Server-side request forgery in the Google Photos picker in Event Gallery extension < 6.6.0 - The Google Photos picker of the back-end upload page fetches the thumbnails of the picked images through the server, with the OAuth access token of the Google Photos account. The task took the address to fetch from the request without checking it and asked for no form token. A prepared page on another web site could therefore make the server send the access token of the account to any address, or fetch addresses inside the server's network, in the name of a logged in administrator; a back-end user with the permission "Manage" could do the same directly. The token is valid for about an hour and reaches what the picker session of the account reaches.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-102777?

It affects 1 product.


Products: Svenbluege Event Gallery.

## How do I fix CVE-2026-102777?

No fix has been published for CVE-2026-102777 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-102777 being exploited?

There is no known exploitation of CVE-2026-102777 in the wild and no public exploit code.

## Other vulnerabilities in svenbluege.de Event Gallery for Joomla

- [CVE-2026-97164](https://insights.sbomify.com/CVE-2026-97164/): Joomla Extension - svenbluege.de - Path Traversal in Clear Cache task in Event Gallery extension < 6.5.0 (high 7.0)
- [CVE-2026-100748](https://insights.sbomify.com/CVE-2026-100748/): Joomla Extension - svenbluege.de - CSRF in various cart actions in Event Gallery extension < 6.5.0 (medium 6.9)
- [CVE-2026-102778](https://insights.sbomify.com/CVE-2026-102778/): Cross-site scripting in Event Gallery for Joomla (medium 5.3)
- [CVE-2026-97165](https://insights.sbomify.com/CVE-2026-97165/): Joomla Extension - svenbluege.de - Reflected XSS and open redirect in Event Gallery extension < 6.5.0 (medium 5.3)
- [CVE-2026-102776](https://insights.sbomify.com/CVE-2026-102776/): Cross-site request forgery in Event Gallery for Joomla (medium 5.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-102777 and fix it if it is affected.

What it is: CVE-2026-102777 is a medium-severity server-side request forgery vulnerability in svenbluege.de Event Gallery for Joomla, published on 5 Oct 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-102777 in the wild and no public exploit code.

Affected product: svenbluege.de Event Gallery for Joomla. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-102777/ (Markdown: https://insights.sbomify.com/CVE-2026-102777/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-102777
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-102777
- OSV: https://osv.dev/vulnerability/CVE-2026-102777

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-102777/
Summaries are generated and may contain mistakes; the official description above is the record.