this post was submitted on 28 Nov 2025
568 points (98.3% liked)

Selfhosted

60451 readers
949 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Detailed Rules Post

  1. Be civil.

  2. No spam.

  3. Posts are to be related to self-hosting.

  4. Don't duplicate the full text of your blog or readme if you're providing a link.

  5. Submission headline should match the article title.

  6. No trolling.

  7. Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 3 years ago
MODERATORS
 

Plex is starting to enforce its new rules, which prevent users from remotely accessing a personal media server without a subscription fee.

If anyone needs it: https://jellyfin.org/

you are viewing a single comment's thread
view the rest of the comments
[–] fartsparkles@lemmy.world 3 points 7 months ago (2 children)

You’re aware those CVEs are only relevant for ancient versions of Plex and were fixed long ago?

[–] Mondez@lemdro.id 1 points 7 months ago

Those are the the ones that somone has managed to find in closed source software...

[–] tyler@programming.dev 0 points 7 months ago (1 children)

They are not marked as resolved.

[–] fartsparkles@lemmy.world 1 points 7 months ago* (last edited 7 months ago)

CVEs don’t get issued “resolved” statuses… They are either reserved, published, or rejected (technically NVD have a few extra for published). That’s just junk data in that tool you’re using. Use authoritative sources like cve.org or nvd.nist.gov.

You can see the CPEs on NVD and they’re old versions of Plex (and were old when the vulns were published).