HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
AdvancedCustomFields
acf
PHP2024–2024
AdvancedCustomFields / acf

acf

Advanced Custom Fields

3Distinct people
3Mentions
0Explicit recommenders
948GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Advanced Custom Fields

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 12:54:37 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by 6-hour interval3 dated mentions

Observed mentions: 2024-10-12 20:02:56 UTC to 2024-10-16 18:24:01 UTC.

012024-10-12 18:00:00 UTC to 2024-10-13 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsOct 12, 18:002024-10-13 00:00:00 UTC to 2024-10-13 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-10-13 06:00:00 UTC to 2024-10-13 12:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2024-10-13 12:00:00 UTC to 2024-10-13 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-10-13 18:00:00 UTC to 2024-10-14 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-10-14 00:00:00 UTC to 2024-10-14 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-10-14 06:00:00 UTC to 2024-10-14 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-10-14 12:00:00 UTC to 2024-10-14 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-10-14 18:00:00 UTC to 2024-10-15 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsOct 14, 18:002024-10-15 00:00:00 UTC to 2024-10-15 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-10-15 06:00:00 UTC to 2024-10-15 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-10-15 12:00:00 UTC to 2024-10-15 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-10-15 18:00:00 UTC to 2024-10-16 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-10-16 00:00:00 UTC to 2024-10-16 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-10-16 06:00:00 UTC to 2024-10-16 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-10-16 12:00:00 UTC to 2024-10-16 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-10-16 18:00:00 UTC to 2024-10-17 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsOct 16, 18:00

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Oct 12, 18:002024-10-12 18:00:00 UTC2024-10-13 00:00:00 UTC101
Oct 13, 00:002024-10-13 00:00:00 UTC2024-10-13 06:00:00 UTC000
Oct 13, 06:002024-10-13 06:00:00 UTC2024-10-13 12:00:00 UTC101
Oct 13, 12:002024-10-13 12:00:00 UTC2024-10-13 18:00:00 UTC000
Oct 13, 18:002024-10-13 18:00:00 UTC2024-10-14 00:00:00 UTC000
Oct 14, 00:002024-10-14 00:00:00 UTC2024-10-14 06:00:00 UTC000
Oct 14, 06:002024-10-14 06:00:00 UTC2024-10-14 12:00:00 UTC000
Oct 14, 12:002024-10-14 12:00:00 UTC2024-10-14 18:00:00 UTC000
Oct 14, 18:002024-10-14 18:00:00 UTC2024-10-15 00:00:00 UTC000
Oct 15, 00:002024-10-15 00:00:00 UTC2024-10-15 06:00:00 UTC000
Oct 15, 06:002024-10-15 06:00:00 UTC2024-10-15 12:00:00 UTC000
Oct 15, 12:002024-10-15 12:00:00 UTC2024-10-15 18:00:00 UTC000
Oct 15, 18:002024-10-15 18:00:00 UTC2024-10-16 00:00:00 UTC000
Oct 16, 00:002024-10-16 00:00:00 UTC2024-10-16 06:00:00 UTC000
Oct 16, 06:002024-10-16 06:00:00 UTC2024-10-16 12:00:00 UTC000
Oct 16, 12:002024-10-16 12:00:00 UTC2024-10-16 18:00:00 UTC000
Oct 16, 18:002024-10-16 18:00:00 UTC2024-10-17 00:00:00 UTC101

What Hacker News says

3 sources
I don't intend to defend Automattic's shitty behavior at all, it's indisputably shitty and I take offense at your suggestions that I may think otherwise, as I never gave you any reason to believe that. That said, you clearly seem to be confused about the nature of the issue being fixed there. It's clear from the existing code that the contract between this function and the callback getting executed is that the callback is expected to execute in a kind of a sanitized environment with restricted execution abilities. You can argue that it's a really weak sandbox and that the whole design is smelly, and I'll agree with you. However, that's how this code was designed and that's what users are running on their servers, and that's how they expect it to behave. It prevents the callback from calling functions with `wp_` prefix and it disallows it
Read the rest
from reading or making changes to user's POST data. Now, if you find a way to circumvent those restrictions, it's an obvious security issue. Someone may have deployed some code that relied on that contract, and now that contract is known to be invalid (it always had been, but it wasn't known before). Therefore, stopping that from happening is a security fix. It may be a poor fix - and in fact, this one is, as it's incomplete. But it's a fix. The upstream project recognized that and applied a similar, but a bit more thorough approach in its repo: https://github.com/AdvancedCustomFields/acf/commit/a60034f8a... It does exactly what the change we're discussing does, plus a bit more. You still wouldn't convince me that it's a bulletproof sandbox and I already have some other ideas in my head on how it could potentially be circumvented after reading that code (though my PHP is so rusty I may very well be wrong), but the change in question is clearly a security fix, recognized and applied by both Automattic and WP Engine and I really can't understand why you're so keen on implying otherwise. As I already said, it only made your other (good) points seem weaker.
In Secure Custom Fields by WordPress.org

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.