CVE-2022-25778
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in Web UI of Secomea GateManager allows phishing attacker to issue get request in 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 confidenceCross-Site Request Forgery (CSRF) vulnerability in the Web UI of Secomea GateManager allows remote attackers to trick authenticated users into executing unintended GET requests via malicious links or phishing pages, leveraging the user's active session.
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< 9.7.622134021< 9.7.622134021< 9.7.622134021< 9.7.622134021CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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 your GateManager modelAccess the device admin console or check the physical device label to determine if it is a 4250, 4260, 8250, or 9250 modelAffected if The model is one of the four listed variants (4250, 4260, 8250, or 9250)
-
Check the installed firmware versionLog into the GateManager admin interface and navigate to System > Firmware or Status page to view the current firmware version numberAffected if The firmware version is lower than 9.7.622134021 (for example, 9.6.x or earlier)
-
Verify the Web UI is accessibleConfirm that the GateManager Web UI is reachable from network browsers or external clientsAffected if The Web UI is enabled and accessible, creating a session that could be exploited via CSRF
-
Inspect cookies for SameSite attributeLog into the Web UI, open browser developer tools, go to Application > Cookies, and check if the session cookies have the SameSite attribute set to Strict or LaxAffected if Cookies lack SameSite attribute or have it set to None, indicating missing CSRF protection
You are affected if your GateManager model is 4250/4260/8250/9250 AND the firmware version is below 9.7.622134021 AND the Web UI is accessible to users.
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.
dbcve · scoped9.7.622134021
Implement anti-CSRF tokens for state-changing operations and configure SameSite cookie attributes to prevent cross-origin request forgery. Additionally, validate Origin/Referer headers on sensitive requests.
Gatemanager firmware version 9.7.622134021 or later
- Access the GateManager administrative interface
- Navigate to the firmware upgrade section
- Verify current firmware version is below 9.7.622134021
- Download firmware version 9.7.622134021 or later from Secomea's official support site
- Upload and apply the new firmware following vendor instructions
- Reboot the device as prompted
- Confirm the new firmware version is 9.7.622134021 or higher
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation8.0 h
- Testing4.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 $4,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-25778 — 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-2022-25778 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