CVE-2025-1113
taisan tarzan-cms Add Theme admin#themes upload deserialization
Public exploit available. Not confirmed exploited in the wild yet. No fix published yet.
What to do
No fixed build or workaround is published yet. Limit exposure and watch for a patch.
Steps
Written by AI from the record- Check whether you run tarzan-cms and whether its version is 1.0.0 or earlier.
- Restrict administrator accounts to trusted staff, remove unused accounts, and require strong unique passwords.
- Do not allow untrusted users to upload themes; review recent theme uploads and administrator activity for anything unexpected.
- Contact the vendor or maintainer for a fixed release, because no patch or fixed version is currently available.
- If you cannot control administrator access, take the affected site out of public service until you can.
What it is
From the CVE record
A vulnerability was found in taisan tarzan-cms up to 1.0.0. It has been rated as critical. This issue affects the function upload of the file /admin#themes of the component Add Theme Handler. The manipulation leads to deserialization. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used.
In plain language
Written by AI from the recordTarzan CMS versions up to 1.0.0 have a theme-upload flaw that a logged-in attacker may use to interfere with the site, so affected businesses should address it soon.
Authenticated remote deserialization through the Add Theme upload handler at /admin#themes can compromise confidentiality, integrity, and availability in tarzan-cms.
If you're affected
- Website administration compromise
- Site content changes
- Service disruption
- Sensitive site data exposure
Exploitation
Where each signal puts this CVE on the scale from published to confirmed exploited.
- CISA KEV
Not in the catalog. CISA has not confirmed exploitation.
- Public exploits
1 source with a proof of concept or module.
Exploit links, PoCs and Metasploit modules after sign-in- EPSS
0.5% chance of exploitation activity in the next 30 days, which ranks it in the 43rd percentile of scored CVEs.
Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.
Lifecycle
5 events over 393 days, from the signal feeds we watch.
- Public exploit / PoCsource: other
- Record updated
- Publishedweakness classified, att&ck mapped
Affected products
Technical detail
CVSS 3.1 vector
Open in the CVSS calculatorCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
Scored 6.3 by NVD.
How it is reached
- Attack Vector NetworkExploitable remotely over the network without any special conditions
- Attack Complexity LowNo special conditions — the attack can be reliably reproduced
- Privileges Required LowRequires basic user-level privileges
- User Interaction NoneNo user interaction needed — fully automated exploitation
Scope
- Scope UnchangedImpact is limited to the vulnerable component itself
Impact if exploited
- Confidentiality LowSome restricted information is disclosed, but limited in scope
- Integrity LowData modification is possible but limited in scope or consequence
- Availability LowReduced performance or intermittent disruption of service
Weaknesses
ATT&CK techniques
Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.
Sources
References in the record
Watch the software you run.
My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.
We'll flag the next CVE, public exploit or patch for Tarzan-cms, not every advisory. This one: public exploit.
A free account adds
- The full version matrix and every affected product
- Exploit links, proofs of concept and Metasploit modules
- Email alerts for the products you watch
- The same data over REST API, MCP and CLI