Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2026-8353: Concrete CMS version 9.0 to 9.5.0 is vulnerable to Stored XSS via page name in the Atomik theme

18
Routine
MEDIUM 4.8UPGRADE

CVE-2026-8353 is a medium-severity flaw (CVSS 4.8) affecting concrete cms. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Concrete CMS version 9.0 to 9.5.0 is vulnerable to Stored XSS via page name in the Atomik theme. A rogue editor can inject arbitrary JavaScript that executes in the context of any authenticated user visiting the affected account pages. This can lead to session hijacking, credential theft, malicious actions performed on behalf of users, and potential privilege escalation. The Concrete CMS security team gave this vulnerability a CVSS v.4.0 score of

Why this priority

  • No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score4.8 (Medium)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededHigh
User interactionRequired
EPSS exploit chance0.1% (top 96%)
CISA exploited listNo
WeaknessCWE-79
Published2026-05-22
Last modified2026-07-23
Publisher (CNA): ConcreteCMS · Vendor: concretecms

Share: LinkedIn · X · Reddit

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

Am I affected?

Timeline

concretecms concrete cms UPGRADE
Affected: >= 9.0 and < 9.5.1
Fixed in: 9.5.1
Safe to downgrade to: a release before 9.0
1. Check installed version
apt-cache policy concrete-cms || rpm -q concrete-cms || concrete-cms --version
2. UPGRADE to 9.5.1 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade concrete-cms
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade concrete-cms
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 9.0 (Debian / Ubuntu)
apt-cache madison concrete-cms sudo apt install concrete-cms=<VERSION_BEFORE_9.0> sudo apt-mark hold concrete-cms
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list concrete-cms sudo dnf downgrade concrete-cms-<VERSION_BEFORE_9.0> sudo dnf versionlock add concrete-cms
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
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-2026-8353?

concrete cms: upgrade to 9.5.1. Exact commands for each OS are on this page.

Is CVE-2026-8353 being exploited?

CVE-2026-8353 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-2026-8353 affect?

CVE-2026-8353 affects concrete cms. Severity is medium (CVSS 4.8). Concrete CMS version 9.0 to 9.5.0 is vulnerable to Stored XSS via page name in the Atomik theme. A rogue editor can inject arbitrary JavaScript that executes in the context of any authenticated user visiting the affected account pages. This

How urgent is CVE-2026-8353?

Priority 18/100. No elevated risk signals yet.

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.