Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Security vulnerability: Podlove Web Player Plugin vulnerable to Broken Access Control #128

Open
gerbsen opened this issue Nov 16, 2023 · 4 comments

Comments

@gerbsen
Copy link

gerbsen commented Nov 16, 2023

Hey there, today my Wordfence Plugin for Wordpress gave me the following message during it's routine scan which got me a bit scared.

PNG-Bild

More infos on the CVE can be found here. According to Wordfence the Webplayer:

The Podlove Web Player plugin for WordPress is vulnerable to unauthorized access due to a missing capability check on an unknown function in versions up to, and including, 5.7.1. This makes it possible for unauthenticated attackers to perform an unauthorized action.

What should I do? Disable the plugin for now? Will there be a patch available? Can I somehow block the attack any other way? Thank you for any info on the matter!

@alexander-heimbuch alexander-heimbuch transferred this issue from podlove/podlove-ui Nov 16, 2023
@alexander-heimbuch
Copy link
Contributor

Hey Gerbsen,
thanks for the report. We are already aware of this report and trying to get more information about the potential security issue.

@RealKolago
Copy link

Any progress with the security issue?

@alexander-heimbuch
Copy link
Contributor

The original source of this vulnerability is still not disclosed (see https://patchstack.com/database/vulnerability/podlove-web-player/wordpress-podlove-web-player-plugin-5-7-1-broken-access-control-vulnerability). Also the assigned CVE (https://www.cve.org/CVERecord?id=CVE-2023-47691) doesn't provide any information to resolve it :/

@alexander-heimbuch
Copy link
Contributor

I've got the information what needs to be fixed and prepared a fix, will ping back patchstack about this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants