CVE-2025-22918
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 · uneditedPolycom RealPresence Group 500 <=20 has Insecure Permissions due to automatically loaded cookies. This allows for the use of administrator functions, resulting in the leakage of sensitive user information.
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 confidencePolycom RealPresence Group 500 devices version 20 and below have insecure permissions stemming from automatically loaded cookies. This configuration flaw allows attackers to bypass authentication and access administrator functions, resulting in the exfiltration of sensitive user information.
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 device is Polycom RealPresence Group 500Access the device web interface or check the device status menu to verify the exact model number matches Polycom RealPresence Group 500Affected if Device model is not Polycom RealPresence Group 500
-
Check installed firmware versionLog into the device administrative interface and navigate to System > System Information or Settings > About to view the installed firmware version numberAffected if Firmware version is 20 or below (20.x and any version lower than 20)
-
Verify web interface accessibilityDetermine if the device web administrative interface (typically HTTP/HTTPS on common ports) is reachable from network segments outside the trusted internal networkAffected if Web interface is exposed to untrusted or external networks without firewall protection
-
Inspect authentication and session configurationLog into the device admin panel and review Security or Session settings for cookie-based authentication, remember me features, or persistent login configurations that may allow automatic session initializationAffected if Cookie-based automatic authentication or persistent sessions are enabled with weak permission controls
The environment is affected if a Polycom RealPresence Group 500 device runs firmware version 20 or below, has its web administrative interface network-accessible, and uses automatic cookie-based authentication that permits unauthorized administrator access.
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 dataUpgrade Polycom RealPresence Group 500 firmware to a version newer than 20. If immediate patching is not feasible, restrict network access to the administrative interface using firewall rules or VPN authentication.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.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 $3,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-22918 — 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-2025-22918 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