Plugins · quote-comments · data as of 2026-11-04
Is Quote Comments safe? Known vulnerabilities and latest version
- Status
- Closed 2025-12-22
- Known issues on record
- 2
- Unpatched in latest
- 0
What to do
- Replace it. A closed plugin gets no updates through WordPress, so any hole found from now on stays open.
- Deactivate and delete it once you have a replacement (Plugins → Deactivate → Delete). Deleting removes its files; deactivating alone leaves them on the server.
- If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan, or have us clean it: Emergency Cleanup, $499.
With WP-CLI, once you have a replacement: wp plugin deactivate quote-comments && wp plugin delete quote-comments
Check your version
Known vulnerabilities
2 on record, newest first. “Affected” is the version range the source gives; “fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version. 2 record(s) do not state which versions are affected.
medium 4.3 CVE-2025-14370 · published 2026-01-07
Missing authorization check in Quote Comments (3.0.0 and older)
- Affected
- 3.0.0 and older
- Fixed in
- unknown
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber)
- Range from
- CVE record (the advisory publisher) · score by Wordfence
Details from the advisory
The Quote Comments plugin for WordPress is vulnerable to Missing Authorization in all versions up to, and including, 3.0.0. This is due to missing authorization checks in the quotecomments_add_admin function. This makes it possible for authenticated attackers, with Subscriber-level access and above, to update arbitrary plugin options via the 'action' parameter.
high 7.1 CVE-2025-25156 · published 2025-02-07
Cross-site request forgery (CSRF) in Quote Comments (3.0.0 and older)
- Affected
- 3.0.0 and older
- Fixed in
- unknown
- Access needed (per CVSS)
- No login needed; someone on the site has to click a link or open a page
- Range from
- CVE record (the advisory publisher) · score by Patchstack
Details from the advisory
Cross-Site Request Forgery (CSRF) vulnerability in Stanko Metodiev Quote Comments quote-comments allows Stored XSS.This issue affects Quote Comments: from n/a through <= 3.0.0.
Recent activity
- 2025-12-22 — closed on wordpress.org (Security Issue).
- 2026-01-07 — Missing authorization check disclosed (CVE-2025-14370), fix version not stated.
- 2025-02-07 — Cross-site request forgery (CSRF) disclosed (CVE-2025-25156), fix version not stated.
Get an email when Quote Comments has a new vulnerability
Free. We check the CVE feeds every day and email you only when a new issue for Quote Comments (quote-comments) is published or a fix ships. Unsubscribe in one click.
Browse vulnerabilities
Types found in this plugin: Missing authorization (1) · Cross-site request forgery (CSRF) (1)
Where this data comes from
- Version, last update, installs, closure: wordpress.org/plugins/quote-comments (Plugins API), fetched 2026-11-04.
- Vulnerabilities: NIST National Vulnerability Database (NVD), checked 2026-11-04. This product uses data from the NVD API but is not endorsed or certified by the NVD.
- Each record links to its CVE page and to the original advisory (Wordfence, Patchstack or WPScan) where there is one. We only list a CVE here when its references or its advisory name this exact plugin, so a few real issues may be missing; none should be about a different plugin. Spot an error? Email Daniel.
Badge for your site or docs (states facts with a date, not a verdict):
<a href="https://laskyr.com/plugins/quote-comments"><img src="https://laskyr.com/plugins/quote-comments/badge.svg" alt="Quote Comments vulnerability status"></a>