CVE-2025-58792
Unknown Unknown - Not Provided
BaseFortify

Publication date: 2025-09-05

Last updated on: 2026-04-23

Assigner: Patchstack

Description
Cross-Site Request Forgery (CSRF) vulnerability in WPKube Authors List authors-list allows Cross Site Request Forgery.This issue affects Authors List: from n/a through <= 2.0.6.2.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-09-05
Last Modified
2026-04-23
Generated
2026-05-27
AI Q&A
2025-09-05
EPSS Evaluated
2026-05-25
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
wordpress authors_list_plugin 2.0.6.1
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-352 The web application does not, or cannot, sufficiently verify whether a request was intentionally provided by the user who sent the request, which could have originated from an unauthorized actor.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

This vulnerability is a Cross-Site Request Forgery (CSRF) in the WordPress Authors List Plugin up to version 2.0.6.1. It allows an attacker to trick authenticated users with higher privileges into performing unauthorized actions on the site without their consent. This can compromise the site's security by exploiting the trust a site has in the user's browser. [1]


How can this vulnerability impact me? :

The vulnerability can lead to unauthorized actions being executed on your site by tricking privileged users, potentially compromising site security. Although the severity is rated low (CVSS 4.3), it can still allow attackers to perform actions that the user did not intend, which may affect the integrity of your site. No official patch is available, but virtual patching can mitigate the risk. [1]


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

There are no specific detection commands or network/system detection methods provided for this vulnerability. Users are advised to monitor for updates and consider virtual patching, but no direct detection commands are mentioned. [1]


What immediate steps should I take to mitigate this vulnerability?

Immediate mitigation steps include applying virtual patching (vPatching) to auto-mitigate the security issue without impacting performance, as no official patch or fixed version is currently available. Users should also monitor for updates from the plugin maintainers. [1]


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