CVE-2026-29598
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 · uneditedMultiple stored cross-site scripting (XSS) vulnerabilities in the submit_add_user.asp endpoint of DDSN Interactive Acora CMS v10.7.1 allow attackers to execute arbitrary web scripts or HTML via injecting a crafted payload into the First Name and Last Name parameters.
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 confidenceStored cross-site scripting (XSS) vulnerabilities exist in the submit_add_user.asp endpoint of DDSN Interactive Acora CMS v10.7.1. Attackers can inject malicious scripts into the First Name and Last Name fields when creating new users. Since this is stored XSS, the payload persists in the application and executes whenever other users view the affected user data.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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 Acora CMS versionLocate the version information in the application - typically found in the admin dashboard under 'About' or 'System Info', or check version files in the web root directory. Compare the installed version to v10.7.1.Affected if The installed version matches 10.7.1 or falls within the affected range around this version.
-
Verify submit_add_user.asp existsAccess the submit_add_user.asp endpoint through the web browser or by making an HTTP request to the path (typically /admin/submit_add_user.asp or /submit_add_user.asp). Check if the page loads and presents a user creation form.Affected if The endpoint exists and is accessible, indicating the vulnerable component is present.
-
Confirm user creation is enabledLog in to the Acora CMS admin panel and navigate to the user management section. Verify that the functionality to create new users is available and operational.Affected if User creation functionality is enabled and accessible to the attacker.
-
Inspect database for stored XSS payloadsQuery the user database table (typically named users or similar) and examine the first_name and last_name columns for any suspicious patterns such as <script>, javascript:, onerror=, or other HTML/script tags.Affected if The database contains user records with malicious script payloads in First Name or Last Name fields.
-
Review user list in admin panelView the list of users in the admin interface. Observe whether any user entries trigger JavaScript execution or display abnormal behavior when rendered in the browser.Affected if Users with XSS payloads in name fields are present and render unsafely in the UI.
A user is affected if they are running Acora CMS v10.7.1 (or an affected version), the submit_add_user.asp endpoint exists and is accessible, and malicious scripts are found stored in the First Name or Last Name database fields.
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 robust server-side input validation and output encoding for all user-supplied fields in the user creation functionality. Sanitize or reject HTML/script tags at the server level before storing user input, and ensure proper context-aware output encoding when displaying user data.
- Consultation2.0 h
- Implementation3.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-29598 — 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-2026-29598 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