CVE-2024-1516: The WP eCommerce plugin for WordPress is vulnerable to unauthorized arbitrary post creation due to a missing c

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

wp ecommerce: upgrade to newer than 3.15.1. Exact commands for each OS are on this page.

Q: Is CVE-2024-1516 being exploited?

CVE-2024-1516 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-1516 affect?

CVE-2024-1516 affects wp ecommerce. Severity is medium (CVSS 5.3). The WP eCommerce plugin for WordPress is vulnerable to unauthorized arbitrary post creation due to a missing capability check on the check_for_saas_push() function in all versions up to, and including, 3.15.1. This makes it possible for una

Q: How urgent is CVE-2024-1516?

Priority 33/100. Remotely exploitable, no login, no user action

Routine

MEDIUM 5.3REMOTEUPGRADE

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

The WP eCommerce plugin for WordPress is vulnerable to unauthorized arbitrary post creation due to a missing capability check on the check_for_saas_push() function in all versions up to, and including, 3.15.1. This makes it possible for unauthenticated attackers to create arbitrary posts with arbitrary content.

Why this priority

Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	5.3 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.4% (top 64%)
CISA exploited list	No
Weakness	CWE-862
Published	2024-02-28
Last modified	2026-06-17

Publisher (CNA): Wordfence · Vendor: zao

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

Am I affected?

Timeline

2024-02-28 09:15 UTCPublished CVE record published
2026-06-17 07:04 UTCUpdated Record last modified

zao wp ecommerce UPGRADE

Affected: <= 3.15.1

Fixed in: newer than 3.15.1

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy wp-ecommerce || rpm -q wp-ecommerce || wp-ecommerce --version

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

sudo apt update && sudo apt install --only-upgrade wp-ecommerce

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade wp-ecommerce

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-1516?

wp ecommerce: upgrade to newer than 3.15.1. Exact commands for each OS are on this page.

Is CVE-2024-1516 being exploited?

CVE-2024-1516 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-1516 affect?

CVE-2024-1516 affects wp ecommerce. Severity is medium (CVSS 5.3). The WP eCommerce plugin for WordPress is vulnerable to unauthorized arbitrary post creation due to a missing capability check on the check_for_saas_push() function in all versions up to, and including, 3.15.1. This makes it possible for una

How urgent is CVE-2024-1516?

Priority 33/100. Remotely exploitable, no login, no user action

Software pages

WordPress vulnerabilities

Related CVEs

CVE-2024-1514 CRITICAL 9.8 UPGRADE The WP eCommerce plugin for WordPress is vulnerable to time-based blind SQL Injection via the 'cart_contents'

References

← Back to latest CVEs