CVE-2026-57316 WordPress GetGenie plugin <= 4.4.2 - Sensitive Data Exposure vulnerability
Medium 6.5
Published
Updated
Check this codebase for CVE-2026-57316 and fix it if it is affected.
What it is: CVE-2026-57316 is a medium-severity vulnerability in Roxnor GetGenie, published on 26 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-57316 in the wild and no public exploit code.
Affected product: Roxnor GetGenie. 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-57316/ (Markdown: https://insights.sbomify.com/CVE-2026-57316/index.md)
Attackers can expose sensitive subscriber data in the GetGenie WordPress plugin, requiring an upgrade to secure user information.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-57316?
CVE-2026-57316 is a medium-severity vulnerability in Roxnor GetGenie, published on 26 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
Subscriber Sensitive Data Exposure in GetGenie <= 4.4.2 versions.
Weakness: CWE-497
Which versions are affected by CVE-2026-57316?
How do I fix CVE-2026-57316?
No fix has been published for CVE-2026-57316 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-57316 being exploited?
There is no known exploitation of CVE-2026-57316 in the wild and no public exploit code.
Sources
Also known as GHSA-3rvx-h374-mgc3.