CVE-2023-53914
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedUliCMS 2023.1 contains an authentication bypass vulnerability that allows unauthenticated attackers to create admin users through mass assignment in the UserController. Attackers can send a crafted POST request to the admin index.php endpoint with specific parameters to generate an administrative account with full system access.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceUliCMS 2023.1 contains an authentication bypass vulnerability in the UserController that allows unauthenticated attackers to create administrative user accounts through mass assignment. Attackers send a crafted POST request to the admin index.php endpoint with specific parameters to gain full system access via a newly created admin account.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 2023.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm UliCMS versionLocate the version file or check the admin dashboard footer for the installed UliCMS version numberAffected if The installed version is exactly 2023.1 (this specific version is affected)
-
Verify admin endpoint exposureSend a test HTTP request to yourdomain.com/admin/index.php from an unauthenticated external IP address and check if the page loads or responds without a 403/401 errorAffected if The admin/index.php endpoint is accessible without authentication from the internet or untrusted networks
-
Review access logs for suspicious user creation requestsSearch web server access logs (typically in /var/log/apache2/ or /var/log/nginx/) for POST requests to admin/index.php containing user-related parameters such as 'user', 'username', 'password', 'role', or 'admin' from unexpected IP addressesAffected if There are POST requests to admin/index.php with user creation parameters from unknown or external IP addresses
-
Audit existing administrative accountsQuery the database or use the admin panel to list all user accounts with administrative privileges, then verify each account was created by an authorized administratorAffected if There are administrative accounts that were not created by known, authorized administrators
If you are running UliCMS version 2023.1 and the admin/index.php endpoint is externally accessible, your system is vulnerable to unauthenticated admin account creation; additionally, check for existing unauthorized admin accounts as evidence of exploitation.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply the vendor patch or update to a patched version of UliCMS that addresses the mass assignment vulnerability in the UserController and restricts admin user creation to authenticated, authorized sessions.
- Consultation3.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,832.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-53914 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-53914 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data