CVE-2023-26951
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 · uneditedonekeyadmin v1.3.9 was discovered to contain a stored cross-site scripting (XSS) vulnerability via the Member List module.
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 · moderate confidenceonekeyadmin v1.3.9 contains a stored XSS vulnerability in the Member List module. User-supplied input in the member list functionality is not properly sanitized before being rendered, allowing malicious scripts to persist and execute when other users view the affected member data.
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= 1.3.9CVSS 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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
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.
-
Identify installed Onekeyadmin versionLocate the version file or admin panel footer/version display - common locations include version.php, a config file, or the admin dashboard footer. Compare the version number to the affected version 1.3.9.Affected if The installed version is exactly 1.3.9
-
Confirm Member List module is activeAccess the admin panel and navigate to the Member List module. Check if the module is installed, enabled, and accessible in the navigation menu or dashboard.Affected if The Member List module exists and is accessible in the application
-
Verify member data input accepts unsanitized contentAdd a test member entry containing a harmless script tag in a member field (such as name or description): <script>alert('XSS')</script>. Save the entry and then view the member list.Affected if The script tag executes or appears unescaped when the member list is displayed, indicating lack of output encoding
-
Inspect stored member data in databaseQuery the members table in the database (typically named something like 'members' or 'user' table) and examine stored values for any existing script tags or HTML that were input through the Member List module.Affected if Raw HTML/script tags are stored and retrieved from the database without sanitization
-
Review member list rendering codeExamine the PHP/template files responsible for displaying the member list - look for the code that outputs member field values to HTML. Check if output encoding functions (htmlspecialchars or equivalent) are used.Affected if Member data is output directly to HTML without encoding functions
You are affected if running Onekeyadmin version 1.3.9 with the Member List module enabled and member data is rendered without proper output encoding, allowing stored XSS execution.
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 dataImplement output encoding/sanitization at all display points for member data, apply input validation on submission, and consider Content Security Policy headers as defense-in-depth.
- Consultation3.0 h
- Implementation6.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-26951 — 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-26951 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