DoraCMS through 3.1.0 Mass Assignment via API Key Update Endpoint
Affects DoraCMS 3.0.x to 3.1 (commit 70cf0fc), reproduced on the MongoDB database mode. The checked facts record no vendor rating and no fix.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- Proof of concept public, per CISA
- Fix
- Fix or patch referenced
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Affects DoraCMS versions 3.0.x to 3.1 (commit 70cf0fc). Attacker must hold an ordinary user account on the CMS. Reproduction was on the MongoDB database mode of DoraCMS.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 33/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Fix
- Fix or patch referenced
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: poc
- Automatable: no
- Technical impact: total
Summary
DoraCMS through 3.1.0 contains a mass assignment vulnerability in the PUT /api/v1/user/api-keys/:id endpoint that allows authenticated low-privileged users to rebind their API key to another user's account. Attackers can set the userId field on their own key to a victim's id, then act as that victim to modify profiles and publish or delete content.
What to do
Check whether your setup matches what the bug needs.
Affects DoraCMS versions 3.0.x to 3.1 (commit 70cf0fc). Attacker must hold an ordinary user account on the CMS. Reproduction was on the MongoDB database mode of DoraCMS.Apply the patch listed under Evidence.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: poc · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- doramart DoraCMS
through 3.1.0
Evidence 4
- Patch
- Exploit
- Repository
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-120448
What does this mean?
An account holder can add a userId field to an API key update request, which binds the API key to another user's account. The attacker can then read and modify that user's profile and publish or delete content as that user.Source: vul.yulun.ac.cn
Am I affected, and how do I check?
The advisory lists DoraCMS 3.0.x through 3.1 (commit 70cf0fc), and reproduction was on the MongoDB database mode of the Docker compose deployment. To check an installation, confirm the version and whether it includes commit 70cf0fc, and note which database mode it runs. The attacker needs an ordinary user account on the CMS.Source: vul.yulun.ac.cn
What should I do about it?
The checked facts name no fixed version and no workaround, so no upgrade target can be given here. Check the DoraCMS repository or the advisory for a patched release and update once one is published.Source: vul.yulun.ac.cn
Is it being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked.Source: cve.now feed data