CVE-2024-10847: The Storely theme for WordPress is vulnerable to Stored Cross-Site Scripting via a malicious display name in a

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

storely: upgrade to newer than 16.6. Exact commands for each OS are on this page.

Q: Is CVE-2024-10847 being exploited?

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

CVE-2024-10847 affects storely. Severity is medium (CVSS 6.4). The Storely theme for WordPress is vulnerable to Stored Cross-Site Scripting via a malicious display name in all versions up to, and including, 18 due to insufficient input sanitization and output escaping. This makes it possible for authen

Q: How urgent is CVE-2024-10847?

Priority 27/100. No elevated risk signals yet.

Routine

MEDIUM 6.4UPGRADE

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

The Storely theme for WordPress is vulnerable to Stored Cross-Site Scripting via a malicious display name in all versions up to, and including, 18 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	6.4 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.3% (top 81%)
CISA exploited list	No
Weakness	CWE-79
Published	2025-01-30
Last modified	2026-06-17

Publisher (CNA): Wordfence · Vendor: sellerthemes

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

Am I affected?

Timeline

2025-01-30 14:15 UTCPublished CVE record published
2026-06-17 06:56 UTCUpdated Record last modified

sellerthemes storely UPGRADE

Affected: <= 16.6

Fixed in: newer than 16.6

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy storely || rpm -q storely || storely --version

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

sudo apt update && sudo apt install --only-upgrade storely

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade storely

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

storely: upgrade to newer than 16.6. Exact commands for each OS are on this page.

Is CVE-2024-10847 being exploited?

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

CVE-2024-10847 affects storely. Severity is medium (CVSS 6.4). The Storely theme for WordPress is vulnerable to Stored Cross-Site Scripting via a malicious display name in all versions up to, and including, 18 due to insufficient input sanitization and output escaping. This makes it possible for authen

How urgent is CVE-2024-10847?

Priority 27/100. No elevated risk signals yet.

Software pages

WordPress vulnerabilities

References

← Back to latest CVEs