CVE-2026-121929EmpireSoft EmpireCMS cross-site scripting
CVE-2026-121929 is a cross-site scripting in EmpireSoft EmpireCMS, rated low (2.0 on CVSS 4.0).
Why this priority: Low severity, with no exploitation signal.
Published · Updated · NVD status: Deferred
What it is
Input is written into a web page without escaping, so an attacker's script runs in the browser of anyone who views it. Input is evaluated as code by the application, so an attacker's code runs inside it.
How it is reached
An attacker can exploit it over the network, with an ordinary user account, but someone has to act first, such as opening a file or following a link.
What an attacker gains
The direct impact is limited: partial access to data or a partial outage. In practice, this kind of flaw lets an attacker act inside a signed-in user's browser session.
Is it being exploited?
CISA's SSVC assessment notes a public proof of concept. EPSS estimates a 0.19% chance of exploitation activity in the next 30 days, higher than 9% of scored CVEs.
What to do
- No fixed version is listed yet. Find every place EmpireSoft EmpireCMS runs, watch the references for a fix, and plan a replacement if it is no longer supported.
- While there is no fix, review who holds accounts that can reach it.
- Warn the people who use it, and filter files and links on the way in.
Description from NVD
A security flaw has been discovered in EmpireSoft EmpireCMS up to 8.0. Impacted is an unknown function of the file /e/member/mspace/index.php. The manipulation of the argument spacename results in cross site scripting. It is possible to launch the attack remotely. The exploit has been released to the public and may be used for attacks. The vendor was contacted early about this disclosure but did not respond in any way.
What this means for your architecture.
A CVE names a product. Whether it matters depends on where that product sits in your systems: what reaches it, which trust boundary it guards and what it can reach once compromised. Veriom maps your components, their relationships and your trust boundaries from your code, cloud and delivery evidence, so you can see where a component like this sits. The radar itself does not look at your systems.
Components it touches
- Web front ends and single-page apps. The flaw sits between a user's browser and the web application.
- Admin consoles served to a browser. The flaw sits between a user's browser and the web application.
- Application servers and the hosts they run on. The flaw sits between untrusted input and code or command execution.
- Template engines. The flaw sits between untrusted input and code or command execution.
Trust boundaries in play
- Authenticated network access. An account is needed, so exposure follows who can sign in: customers, partners or staff.
- People who open files and links. Mail, chat and browsers are the delivery path.
- Between a user's browser and the web application. An attacker who crosses it can act inside a signed-in user's browser session.
- Between untrusted input and code or command execution. An attacker who crosses it can run commands or code with the privileges of the affected service.
Questions to answer about your own systems
- Where does EmpireSoft EmpireCMS run in your systems, and at which version?
- Which of those instances can be reached from the internet or partner networks?
- What can it reach once compromised: which data stores, secrets and services?
Sources
- CVE records and CVSS scores from the NVD CVE API. This product uses the NVD API but is not endorsed or certified by the NVD.
- Exploitation status from CISA’s Known Exploited Vulnerabilities catalog.
- Exploit likelihood from FIRST’s Exploit Prediction Scoring System (EPSS), refreshed daily.
- Explanations are written by Veriom from fixed templates over each record’s data, not by a person reviewing each CVE. Descriptions are quoted from the records as published.