CVE-2026-27505
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 · uneditedSVXportal version 2.5 and prior contain a stored cross-site scripting vulnerability in the user registration workflow (index.php submitting to admin/user_action.php). User-supplied fields such as Firstname, lastname, and email are stored in the backend database without adequate output encoding and are later rendered in the administrator interface (admin/users.php), allowing an unauthenticated remote attacker to inject arbitrary JavaScript that executes in an administrator's browser upon viewing the affected page.
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 confidenceSVXportal 2.5 and prior has a stored XSS vulnerability where user registration input fields (Firstname, lastname, email) in index.php are stored to the database via admin/user_action.php without proper input sanitization, and subsequently rendered in admin/users.php without output encoding, allowing arbitrary JavaScript execution in administrator browsers.
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<= 2.5CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Confirm SVXportal installationLocate the web application root directory and identify if index.php contains SVXportal branding or references. Check for the presence of admin/users.php and admin/user_action.php files in the web root.Affected if SVXportal is installed and the admin/users.php file exists in the application.
-
Identify installed versionOpen index.php or any version file in the application root to find the version number. Check common version files like version.php, config.php, or the footer/includes in index.php for version strings.Affected if The version number displayed is 2.5 or lower.
-
Verify user registration is accessibleCheck if the registration functionality exists by accessing the user registration page (typically index.php?page=register or similar). Confirm admin/user_action.php handles user creation.Affected if User registration functionality is enabled and accessible.
-
Check database for suspicious user recordsAccess the database (MySQL/MariaDB) and query the users table: SELECT id, firstname, lastname, email FROM users WHERE firstname LIKE '%<script%' OR lastname LIKE '%<script%' OR email LIKE '%<script%'. Use the database credentials from config.php if available.Affected if Any user records contain HTML script tags or other JavaScript payloads in name or email fields.
-
Inspect admin/users.php for output encodingView the source code of admin/users.php and search for where firstname, lastname, and email variables are echoed/printed. Check if htmlspecialchars() or equivalent encoding is used.Affected if The code prints user input fields directly to HTML without encoding, allowing script tag injection.
If SVXportal version 2.5 or lower is installed and the admin/users.php page renders user data without output encoding, the environment is vulnerable to stored XSS via the user registration 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 input validation during registration and output encoding when rendering user data in the admin interface to prevent XSS execution.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-27505 — 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-27505 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