Technology

59689 readers

3167 users here now

This is a most excellent place for technology news and articles.

Our Rules

Follow the lemmy.world rules.
Only tech related content.
Be excellent to each another!
Mod approved content bots can post up to 10 articles per day.
Threads asking for personal tech support may be deleted.
Politics threads may be removed.
No memes allowed as posts, OK to post as comments.
Only approved bots from the list below, to ask if your bot can be added please contact us.
Check for duplicates before posting, duplicates may be removed

Approved Bots

founded 1 year ago

MODERATORS

[email protected]

310

Backdoor slipped into multiple WordPress plugins in ongoing supply-chain attack (arstechnica.com)

submitted 5 months ago by [email protected] to c/[email protected]

49 comments fedilink hide all child comments

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

[–] [email protected] 13 points 5 months ago (1 children)

That's the ecosystem. WordPress itself is pretty basic, these things attack plugins, and their often not-very-experienced creators and users. The thing with WordPress is that this kind of vulnerability comes with the problem space, not the particular solution. If there was a different product in the same space, it would not fare better by default.

Also, I'd bet that a ton of CVEs are filed for C++ libraries, yet nobody is harping on about how insecure C++ is.

[–] sugar_in_your_tea 3 points 5 months ago

Exactly. A plug-in architecture is a feature, and it's really hard to secure. Instead of going that route, they should have instead solved specific problems. When you make it easy to add someone else's code, you also make it easy to forget to remove it later, or to not stay updated on which plugins are deprecated/abandoned.

A plug-in system is insecure by design for a public-facing service. YAGNI, so pick a handful of stuff you actually need.