CVE-2025-53291
BaseFortify
Publication date: 2025-09-09
Last updated on: 2026-04-23
Assigner: Patchstack
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| spoddev | spreadconnect | * |
Helpful Resources
Exploitability
| 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 WordPress Spreadconnect plugin (versions up to 2.1.5). It occurs due to missing authorization, authentication, or nonce token checks in certain plugin functions, which may allow users with low privileges (such as Subscribers) to perform actions that should be restricted to higher-privileged roles. [1]
How can this vulnerability impact me? :
The impact of this vulnerability is minimal with a low likelihood of exploitation. However, if exploited, it could allow an attacker with Subscriber-level access to perform unauthorized actions reserved for higher-privileged users. This could potentially lead to limited integrity and availability issues within the affected plugin's functionality. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
Detection of this vulnerability involves identifying the presence of the Spreadconnect plugin version 2.1.5 or earlier on your WordPress installation. Since the vulnerability is due to missing authorization checks, manual code review or plugin version checks can help. There are no specific commands provided for detection. It is recommended to monitor for unusual actions performed by users with Subscriber privileges. Additionally, engaging hosting providers for server-side malware scanning or professional incident response services is advised, as plugin-based malware scanners may be unreliable due to potential tampering. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include applying virtual patching (vPatching) offered by Patchstack, which provides automatic protection against this vulnerability without an official fix. Restricting user privileges to minimize Subscriber-level access and monitoring for suspicious activities is also recommended. In case of suspected compromise, engage hosting providers for server-side malware scanning or professional incident response services. Since no official patch is available, virtual patching is the most effective immediate measure. [1]