dbcve.org
Gatemanager 4250 FirmwareOperating system · Secomea

CVE-2022-25781

MEDIUM · 6.1 CVSS v3.1 Published 2022-05-04
Fix available
A fix is available. Upgrade to 9.7.622134021 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
Cross-site Scripting (XSS) vulnerability in Web UI of Secomea GateManager allows phishing attacker to inject javascript or html into logged in user session.

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 confidence

A cross-site scripting (XSS) vulnerability exists in the Web UI of Secomea GateManager that allows an attacker to inject malicious JavaScript or HTML code into the session of a logged-in user. This is likely a reflected or stored XSS flaw where user-supplied input is not properly sanitized before being rendered in the web interface.

MitigationApply vendor-provided patches for Secomea GateManager. If patches are unavailable, implement input validation and output encoding on all user-controllable fields in the Web UI to prevent script injection.

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
Gatemanager 4250 FirmwareOperating system
Affected:< 9.7.622134021
Gatemanager 4260 FirmwareOperating system
Affected:< 9.7.622134021
Gatemanager 8250 FirmwareOperating system
Affected:< 9.7.622134021
Gatemanager 9250 FirmwareOperating system
Affected:< 9.7.622134021

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify GateManager model number
    Locate the model label on the physical device or check the device documentation/packaging for the model number (4250, 4260, 8250, or 9250)
    Affected if The model is one of: 4250, 4260, 8250, or 9250
  2. Determine installed firmware version
    Access the GateManager web interface and navigate to System > Status or System > About to view the firmware version, or use the CLI command 'version' if available
    Affected if The firmware version is lower than 9.7.622134021 for any of the affected models
  3. Confirm web UI is accessible
    Attempt to access the GateManager web UI by entering the device IP or hostname in a web browser
    Affected if The web interface is accessible and responds, meaning the vulnerable component is exposed
  4. Identify web UI input fields
    Log into the web interface and locate user-controllable input fields such as device names, description fields, or configuration parameters
    Affected if Input fields exist in the web interface where user-supplied data could be rendered without sanitization

If the GateManager model is 4250, 4260, 8250, or 9250 and the firmware version is below 9.7.622134021, the web UI is likely vulnerable to XSS via unsanitized input fields.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 9.7.622134021 or later
Fixed in 9.7.622134021
Interim mitigation

Apply vendor-provided patches for Secomea GateManager. If patches are unavailable, implement input validation and output encoding on all user-controllable fields in the Web UI to prevent script injection.

Recommended fix Moderate confidence

Secomea GateManager Firmware 9.7.622134021 or later

  1. 1. Identify the exact current firmware version of the Secomea GateManager device (4250, 4260, 8250, or 9250 model)
  2. 2. Download the firmware version 9.7.622134021 or later from Secomea's official support portal at www.secomea.com
  3. 3. Access the GateManager administrative interface using a secure, trusted network connection
  4. 4. Navigate to the firmware upgrade section in the device management settings
  5. 5. Upload and apply the new firmware version 9.7.622134021 or later
  6. 6. After the upgrade completes, verify the device is operational and confirm the new firmware version is installed
  7. 7. Clear browser cache and test that the Web UI properly sanitizes user input to confirm the XSS vulnerability is remediated
Caveat Review Secomea release notes for any configuration or behavioral changes between your current version and 9.7.622134021; test in a non-production environment first

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Gatemanager 4250 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-25781 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-25781 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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