ZDF
Sign inSign up

Vulnerabilities

Vulnerability · 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.

Published Sep 11, 2025 · catalog updated Apr 8, 2026 · The integration of the AMO.CRM

Check this week

CVE-2025-9628 is not in CISA KEV. FIRST estimates a 16.00% chance of exploitation in the next 30 days. Check whether you run The integration of the AMO.CRM.

Gaps on this record

  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
Medium4.3
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
16.00%
Remediation
Vendor / distro source
Affected products
vendor jh5ru The integration of the AMO.CRM 0 ≤1.0.1

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.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • vendor jh5ru The integration of the AMO.CRM 0 ≤1.0.10 ≤1.0.1

How to fix CVE-2025-9628

  • Recommended remediation

    A vendor or distribution source is linked. Check that advisory for patch availability; this catalog does not invent fix status.

  • Official advisories

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

CVE-2025-9628 is not in CISA KEV. FIRST estimates a 16.00% chance of exploitation in the next 30 days. Check whether you run The integration of the AMO.CRM.

Which versions are affected?

Compare what you have installed with jh5ru The integration of the AMO.CRM 0 ≤1.0.1 0 ≤1.0.1. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

No weakness class is stored. EPSS 16.00%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Technology hubs

WordPress security

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Sep 11, 2025 · EUVD

    Detected

    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 fo

  2. Apr 8, 2026 · EUVD

    Updated

    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 fo

Sources

  • EUVDVulnerability recordEUVD-2025-27667

    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 attacker

    euvd.enisa.europa.eu

References

Freshness

Last verified in this catalog Apr 8, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.