Cybersecurity

cybersecurity@sh.itjust.works

10,770 readers

531 active

36 users here now

c/cybersecurity is a community centered on the cybersecurity and information security profession. You can come here to discuss news, post something interesting, or just chat with others.

THE RULES

Instance Rules

Be respectful. Everyone should feel welcome here.
No bigotry - including racism, sexism, ableism, homophobia, transphobia, or xenophobia.
No Ads / Spamming.
No pornography.

Community Rules

Idk, keep it semi-professional?
Nothing illegal. We're all ethical here.
Rules will be added/redefined as necessary.

If you ask someone to hack your "friends" socials you're just going to get banned so don't do that.

Learn about hacking

Hack the Box

Try Hack Me

Pico Capture the flag

Other security-related communities !databreaches@lemmy.zip !netsec@lemmy.world !securitynews@infosec.pub !cybersecurity@infosec.pub !pulse_of_truth@infosec.pub

Notable mention to !cybersecuritymemes@lemmy.world

founded 3 years ago

moderation log

moderators

kid@sh.itjust.works

Lanky_Pomegranate530@midwest.social

Wordpress remote code execution vulnerability July 17 (www.rapid7.com)

submitted 3 months ago by billbasher@lemmy.world to c/cybersecurity@sh.itjust.works

3 comments fedilink hide all child comments

The vulnerability reportedly allows an unauthenticated attacker to execute code via the WordPress REST API batch endpoint, potentially resulting in complete compromise of the website and its underlying data. No valid account or user interaction is required.

According to the advisory, the vulnerability affects WordPress versions 6.9.0 through 6.9.4 and versions 7.0.0 through 7.0.1. The issue is fixed in WordPress 6.9.5 and 7.0.2. A fix is also included in WordPress 7.1 Beta 2.

WordPress maintainers stated they are forcing updates for affected installations with automatic updates enabled. Administrators should nevertheless verify that each internet-facing WordPress website has successfully upgraded to WordPress 6.9.5, 7.0.2, or another fixed release appropriate for its branch. Workarounds are not recommended at this time.

you are viewing a single comment's thread
view the rest of the comments

[–] glowie@infosec.pub 1 point 3 months ago

I know Cloudflare can be a contentious topic here, but they rolled out a ruleset to their WAF for this to pseudo “patch” the vuln chain, until you can upgrade WP. So, if your clients use the Pro plan or above, they should be safe in the interim.

permalink

fedilink

source

parent