CVE-2025-28985
Awaiting Analysis Awaiting Analysis - Queue
BaseFortify

Publication date: 2025-06-06

Last updated on: 2026-04-23

Assigner: Patchstack

Description
Missing Authorization vulnerability in Elastic Email Elastic Email Subscribe Form elastic-email-subscribe-form allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Elastic Email Subscribe Form: from n/a through <= 1.2.2.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-06-06
Last Modified
2026-04-23
Generated
2026-05-07
AI Q&A
2025-06-06
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Currently, no data is known.
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-862 The product does not perform an authorization check when an actor attempts to access a resource or perform an action.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

This vulnerability is a Broken Access Control issue in the Elastic Email Subscribe Form WordPress plugin (up to version 1.2.2). It occurs due to missing authorization, authentication, or nonce token checks in certain functions, allowing users with only subscriber-level privileges to perform actions that should be restricted to higher-privileged users. The plugin is likely abandoned with no official fix available. [1]


How can this vulnerability impact me? :

The vulnerability allows unprivileged users to perform unauthorized actions, potentially leading to integrity and availability impacts on the affected system. Since the plugin is abandoned and unpatched, the risk remains unless mitigated by virtual patching. This could result in unauthorized changes or disruptions within the WordPress site using this plugin. [1]


How can this vulnerability be detected on my network or system? Can you suggest some commands?

Detection involves checking for unauthorized actions performed by subscriber-level users that should require higher privileges. Since the vulnerability arises from missing authorization checks in the Elastic Email Subscribe Form plugin (up to version 1.2.2), monitoring logs for suspicious access or changes initiated by low-privilege users is recommended. Specific commands are not provided in the resources, but general approaches include reviewing web server access logs and WordPress user activity logs for unusual behavior related to the plugin's functions. [1]


What immediate steps should I take to mitigate this vulnerability?

Immediate mitigation steps include applying a virtual patch (vPatch) offered by Patchstack to auto-mitigate the vulnerability since no official fix or patched version is available. Additionally, users are advised to urgently replace the Elastic Email Subscribe Form plugin with an alternative plugin. Professional incident response and server-side malware scanning are recommended if the site is suspected to be compromised. Simply deactivating the plugin does not eliminate the security risk. [1]


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart