←back to thread

Secure Custom Fields by WordPress.org

(wordpress.org)
172 points ValentineC | 1 comments | 12 Oct 24 18:38 UTC | HN request time: 0s | source
Show context
CharlesW ◴[12 Oct 24 19:27 UTC] No.41821726[source]▶
So WordPress-the-org — which is effectively Matt, as far as I can tell — just Sherlocked a developer's plug-in using the developer's own code, ostensibly as retribution for a security issue that the developer had already fixed. https://www.advancedcustomfields.com/blog/acf-6-3-8-security...

What am I missing?

replies(5): >>41821790 #>>41821829 #>>41821872 #>>41821880 #>>41823351 #
sureIy ◴[12 Oct 24 19:44 UTC] No.41821872[source]▶
> Sherlocked

The verb you're looking for is stole

Sherloking is when a Walmart is built next to a cornershop. Here the dude tore open the corner shop while claiming to be a victim.

replies(2): >>41821969 #>>41821973 #
CharlesW ◴[12 Oct 24 19:56 UTC] No.41821973[source]▶
When I posted, I was under the impression that ACF was open source. But the GitHub repo doesn’t list one, so if it’s not open source…WTF.
replies(3): >>41822031 #>>41822266 #>>41822313 #
ValentineC ◴[12 Oct 24 20:02 UTC] No.41822031[source]▶
> When I posted, I was under the impression that ACF was open source. But the GitHub repo doesn’t list one, so if it’s not open source…WTF.

Isn't it here?

https://github.com/AdvancedCustomFields/acf

If you mean the licence, it's in readme.txt:

https://github.com/AdvancedCustomFields/acf/blob/master/read...

replies(2): >>41822094 #>>41822095 #
1. CharlesW ◴[12 Oct 24 20:10 UTC] No.41822094{3}[source]▶
Thanks! The GitHub app reports it as "None" (https://imgur.com/a/5dyaTfX), but now I see it's "GPLv2 or later".