CSRF in Jh5ru The Integration Of Amo.crm
CVE-2025-9628
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.
Vulnerability class: CSRF (Cross-Site Request Forgery)
Published · last modified .
CVSS v3 metric
CVSS v3 base score 4.3 (Medium). Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N.
EPSS exploit prediction
EPSS: 0.002 (4.8th percentile), scored .
Very low probability of exploitation in the next 30 days; routine patching cadence is appropriate. 5th percentile — 4.8% of CVEs in the catalogue have a lower EPSS than this one. How to read EPSS.
EPSS over last 30 days · oldest: 0.002 · newest: 0.002 · change: 0.000
Affected products
- Jh5ru The Integration Of Amo.crm — versions 0
Weakness classification (CWE)
References
Frequently asked questions
- What is CVE-2025-9628?
- CVE-2025-9628 is a medium-severity vulnerability in Jh5ru The Integration Of Amo.crm, classified under Cross-Site Request Forgery (CSRF). CVSS score: 4.3/10. Published 2025-09-11.
- How severe is CVE-2025-9628?
- Medium severity. CVSS v3 base score is 4.3 out of 10.