CVE-2024-13683: The Automate Hub Free by Sperse.IO plugin for WordPress is vulnerable to Cross-Site Request Forgery in all ver

Q: How do I fix CVE-2024-13683?

automate hub: upgrade to newer than 1.7.0. Exact commands for each OS are on this page.

Q: Is CVE-2024-13683 being exploited?

CVE-2024-13683 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2024-13683 affect?

CVE-2024-13683 affects automate hub. Severity is medium (CVSS 4.3). The Automate Hub Free by Sperse.IO plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.7.0. This is due to missing or incorrect nonce validation on the 'automate_hub' page. This makes it

Q: How urgent is CVE-2024-13683?

Priority 17/100. No elevated risk signals yet.

Routine

MEDIUM 4.3UPGRADE

CVE-2024-13683 is a medium-severity flaw (CVSS 4.3) affecting automate hub. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

The Automate Hub Free by Sperse.IO plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.7.0. This is due to missing or incorrect nonce validation on the 'automate_hub' page. This makes it possible for unauthenticated attackers to update an activation status via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	4.3 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	0.2% (top 91%)
CISA exploited list	No
Weakness	CWE-352
Published	2025-01-24
Last modified	2026-06-17

Publisher (CNA): Wordfence · Vendor: sperse

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2025-01-24 07:15 UTCPublished CVE record published
2026-06-17 07:02 UTCUpdated Record last modified

sperse automate hub UPGRADE

Affected: <= 1.7.0

Fixed in: newer than 1.7.0

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy automate-hub || rpm -q automate-hub || automate-hub --version

2. UPGRADE to newer than 1.7.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade automate-hub

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade automate-hub

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2024-13683?

automate hub: upgrade to newer than 1.7.0. Exact commands for each OS are on this page.

Is CVE-2024-13683 being exploited?

CVE-2024-13683 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2024-13683 affect?

CVE-2024-13683 affects automate hub. Severity is medium (CVSS 4.3). The Automate Hub Free by Sperse.IO plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.7.0. This is due to missing or incorrect nonce validation on the 'automate_hub' page. This makes it

How urgent is CVE-2024-13683?

Priority 17/100. No elevated risk signals yet.

Software pages

WordPress vulnerabilities

References

← Back to latest CVEs