GCVE - cpe:2.3:a:seafile:seafile_server:*:*:*:*:professional:*:*:*

Approved changes feed: RSS · Atom

cpe:2.3:a:seafile:seafile_server:*:*:*:*:professional:*:*:*

part: a version: * update: *

Vendor	Seafile (`9473c929-cd73-551b-8a14-d0f85f6a5ac5`)
Product	Seafile Server (`95388630-3b84-570b-9cb4-611191e83705`)
Edition	*
Language	*
Software edition	professional
Target software	*
Target hardware	*
Other	*
Notes	Imported from gcve-enriched-dumps CVE data

PURL mappings

PURL	Source	Last updated
No PURL mappings for this CPE yet.

Vulnerability references

Identifier	cpeApplicability	Submitted	db.gcve.eu details	Rationale
`CVE:CVE-2026-30587`	vulnerable	2026-06-08 07:57:14.124949	Details available Multiple Stored XSS vulnerabilities exist in Seafile Server version 13.0.15,13.0.16-pro,12.0.14 and prior and fixed in 13.0.17, 13.0.17-pro, and 12.0.20-pro, via the Seadoc (sdoc) editor. The application fails to properly sanitize WebSocket messages regarding document structure updates. This allows authenticated remote attackers to inject malicious JavaScript payloads via the src attribute of embedded Excalidraw whiteboards or the href attribute of anchor tags Published: 2026-03-25T00:00:00.000Z Updated: 2026-05-10T13:02:29.723Z Open on db.gcve.eu Reference links https://gist.github.com/gabdevele/1b7e30ab367b26042fa32f45aa12ce2f https://manual.seafile.com/13.0/changelog/server-changelog/ https://manual.seafile.com/13.0/changelog/changelog-for-seafile-professional-server/ https://manual.seafile.com/12.0/changelog/changelog-for-seafile-professional-server/ https://github.com/haiwen/seahub/commit/4c5301747bdb84c64b2f2b3230417df2d1cc8987	Imported from gcve-enriched-dumps CVE data
`CVE:CVE-2021-43820`	vulnerable	2026-06-08 05:36:44.372921	Permissions check bypass in Seafile HIGH (7.4) Seafile is an open source cloud storage system. A sync token is used in Seafile file syncing protocol to authorize access to library data. To improve performance, the token is cached in memory in seaf-server. Upon receiving a token from sync client or SeaDrive client, the server checks whether the token exist in the cache. However, if the token exists in cache, the server doesn't check whether it's associated with the specific library in the URL. This vulnerability makes it possible to use any valid sync token to access data from any known library. Note that the attacker has to first find out the ID of a library which it has no access to. The library ID is a random UUID, which is not possible to be guessed. There are no workarounds for this issue. Published: 2021-12-14T18:55:10.000Z Updated: 2024-08-04T04:03:09.080Z Open on db.gcve.eu Reference links https://github.com/haiwen/seafile-server/security/advisories/GHSA-m3wc-jv6r-hvv8 https://github.com/haiwen/seafile-server/pull/520	Imported from gcve-enriched-dumps CVE data
`CVE:CVE-2014-5443`	vulnerable	2026-06-08 05:05:47.934631	Details available Seafile Server before 3.1.2 and Server Professional Edition before 3.1.0 allow local users to gain privileges via vectors related to ccnet handling user accounts. Published: 2018-03-19T21:00:00.000Z Updated: 2024-08-06T11:41:49.072Z Open on db.gcve.eu Reference links https://exchange.xforce.ibmcloud.com/vulnerabilities/95458 https://manual.seafile.com/changelog/changelog-for-seafile-professional-server.html https://manual.seafile.com/changelog/server-changelog.html http://www.openwall.com/lists/oss-security/2014/08/24/3 http://www.securityfocus.com/bid/69360	Imported from gcve-enriched-dumps CVE data

Contribute

You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.