CVE-2026-27504
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 reflected cross-site scripting vulnerability in radiomobile_front.php via the stationid query parameter. When an authenticated administrator views a crafted URL, the application embeds the unsanitized parameter value into a hidden input value field, allowing attacker-supplied script injection and execution in the administrator's browser. This can be used to compromise admin sessions or perform unauthorized actions via the administrator's authenticated context.
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 confidenceSVXportal 2.5 and prior contains a reflected XSS vulnerability in radiobile_front.php where the stationid query parameter is directly embedded into a hidden HTML input field without sanitization. When an authenticated administrator clicks a crafted URL, the unsanitized parameter value is rendered in the page, allowing arbitrary JavaScript execution in the admin's browser context.
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 Radioinorr Svxportal installation and versionLocate and examine the Svxportal installation. Check for version indicators such as version files, about pages, or the main application header that displays the software version. Compare your installed version against the affected range: <= 2.5.Affected if The installed version of Radioinorr Svxportal is 2.5 or lower.
-
Locate the vulnerable radiobile_front.php fileSearch the web server document root for the file radiobile_front.php, which is the component identified as containing the XSS vulnerability.Affected if The file radiobile_front.php exists in the Svxportal installation directory.
-
Inspect stationid parameter handling in radiobile_front.phpOpen radiobile_front.php and examine how the stationid query parameter is processed. Look for code that retrieves the stationid from the request and directly embeds it into a hidden HTML input field without sanitization or output encoding.Affected if The code shows the stationid parameter being placed directly into an HTML input field value attribute without sanitization functions such as htmlspecialchars or equivalent encoding.
-
Verify application accessibility for exploitation contextConfirm the Svxportal web interface is accessible and that administrative authentication is required and functional. Since exploitation requires an authenticated administrator to click a crafted URL, verify whether the application is exposed to users who could deliver such links.Affected if The Svxportal administrative interface is accessible to users who could potentially craft and deliver malicious URLs to administrators.
You are affected if Radioinorr Svxportal version 2.5 or earlier is installed, the file radiobile_front.php exists, and the stationid parameter is handled without sanitization in hidden HTML input 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 proper input validation and output encoding for the stationid parameter before rendering it in HTML context. Use context-appropriate encoding (HTML entity encoding) when placing user-supplied values into HTML attributes.
- Consultation2.0 h
- Implementation2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-27504 — 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-27504 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