# CVE-2026-61978: WordPress Secure Card Gateway for ePay Paycenter (Piraeus Bank) plugin <= 1.0.32 - Broken Access Control vulnerability

> Unauthenticated attackers can bypass access controls in the Secure Card Gateway for ePay Paycenter WordPress plugin.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Aug 2026
- **Updated:** 13 Aug 2026
- **Also known as:** GHSA-v764-h2jw-qh28

## What is CVE-2026-61978?

CVE-2026-61978 is a medium-severity missing authorization vulnerability in webhosting4ugr Secure Card Gateway for ePay Paycenter (Piraeus Bank), published on 13 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Unauthenticated Broken Access Control in Secure Card Gateway for ePay Paycenter (Piraeus Bank) <= 1.0.32 versions.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-61978 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-61978 is a medium-severity missing authorization vulnerability in webhosting4ugr Secure Card Gateway for ePay Paycenter (Piraeus Bank), published on 13 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-61978 in the wild and no public exploit code.

Affected product: webhosting4ugr Secure Card Gateway for ePay Paycenter (Piraeus Bank). 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-61978/ (Markdown: https://insights.sbomify.com/CVE-2026-61978/index.md)
```

## Sources

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

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