CVE-2025-9628
Unknown Unknown - Not Provided
BaseFortify

Publication date: 2025-09-11

Last updated on: 2025-09-11

Assigner: Wordfence

Description
The The integration of the AMO.CRM plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.0.1. This is due to missing or incorrect nonce validation on the settings_page function. This makes it possible for unauthenticated attackers to modify critical API connection settings including the AMO.CRM API URL, login credentials, and API hash key via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-09-11
Last Modified
2025-09-11
Generated
2026-05-27
AI Q&A
2025-09-11
EPSS Evaluated
2026-05-25
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
amo crm *
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) issue in the AMO.CRM plugin for WordPress versions up to 1.0.1. It occurs because the plugin's settings_page function lacks proper nonce validation, allowing an attacker to trick a site administrator into performing unintended actions, such as modifying critical API connection settings like the API URL, login credentials, and API hash key, via a forged request.


How can this vulnerability impact me? :

An attacker can exploit this vulnerability to change important API connection settings of the AMO.CRM plugin without authentication by tricking an administrator into clicking a malicious link. This could lead to unauthorized access or manipulation of the CRM integration, potentially disrupting service or exposing sensitive data.


What immediate steps should I take to mitigate this vulnerability?

To mitigate this vulnerability, update the AMO.CRM plugin for WordPress to a version later than 1.0.1 where the nonce validation issue is fixed. Until an update is available, avoid clicking on suspicious links and ensure that only trusted administrators have access to the plugin settings to reduce the risk of CSRF attacks.


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