[wp-trac] [WordPress Trac] #62724: Fix all "Call to undefined function" direct access errors
WordPress Trac
noreply at wordpress.org
Fri Dec 20 13:10:39 UTC 2024
#62724: Fix all "Call to undefined function" direct access errors
------------------------------------+------------------------------
Reporter: bor0 | Owner: (none)
Type: defect (bug) | Status: new
Priority: normal | Milestone: Awaiting Review
Component: General | Version:
Severity: normal | Resolution:
Keywords: has-patch dev-feedback | Focuses:
------------------------------------+------------------------------
Comment (by swissspidy):
This has come up a few times before, for example in #36177, #30806,
#44700, #45773, #48049, or #53271
Per the [https://make.wordpress.org/core/handbook/testing/reporting-
security-vulnerabilities/ Security FAQ], these errors are considered a
server configuration issue rather than a security issue:
> ''' Why are there path disclosures when directly loading certain
files?'''
> This is a server configuration problem. Never enable `display_errors` on
a production site.
Instead of changing all PHP files to add a check for `ABSPATH`, this
should be done in a central location, which is being discussed in #36177.
Let's continue the discussion in that ticket, as it would be best to keep
all discussion on the general idea of "blocking malicious requests" in a
single place, even if any implemented change does not necessarily follow
how the ticket originally intended on it being implemented.
That said, it looks like this ticket is more about unnecessary error
logging rather than a path disclosure. Still, blocking direct access to
the files in question using the web server configuration file should
resolve the issue for now, until any changes are implemented in core.
See also a related similar ticket for bundled themes: #47154.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/62724#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list