| Package | Affected versions | Patched versions |
|---|---|---|
| phpmyfaq/phpmyfaq | ≥ 4.1.1, < 4.1.2 | 4.1.2 |
| thorsten/phpmyfaq | ≥ 4.1.1, < 4.1.2 | 4.1.2 |
A review of phpMyFAQ-main uncovered an authorization issue in the admin-api routes.
Several backend endpoints only check whether the caller is logged in. They do not verify that the caller actually has backend or administrative privileges. As a result, a normal frontend user can access API endpoints that are clearly intended for administrative use.
During local reproduction, a regular user account was able to request /admin/api/index.php/dashboard/versions and receive a successful response from the backend management API.
This issue does not appear to give direct write access in the affected paths that were confirmed, so it should be treated as a backend information disclosure and privilege boundary failure rather than full admin compromise.
The access control split is visible in the controller base class:
public function userIsAuthenticated(): void
{
if (!$this->currentUser->isLoggedIn()) {
throw new UnauthorizedHttpException('Unauthorized access.');
}
}
protected function userHasPermission(PermissionType $permissionType): void
{
// permission-based check
}
The problem is that several Administration\Api controllers use the weaker check even though the routes sit under the backend API namespace.
For example, phpmyfaq/src/phpMyFAQ/Controller/Administration/Api/DashboardController.php exposes:
#[Route(path: 'dashboard/versions', name: 'admin.api.dashboard.versions', methods: ['GET'])]
public function versions(): JsonResponse
{
$this->userIsAuthenticated();
...
}
The same pattern appears in other backend-facing controllers, including:
LdapControllerElasticsearchControllerOpenSearchControllerUpdateControllerThat matters because these endpoints are not part of the normal frontend feature set. They expose backend operational data such as version checks, upgrade state, LDAP configuration, health checks, and search backend status.
Three examples that stand out from an impact perspective are:
GET /admin/api/index.php/ldap/configuration
This can expose LDAP server configuration, mapping settings, group settings, and general authentication-related options. Even with secrets masked, this is still useful internal infrastructure information.
GET /admin/api/index.php/elasticsearch/statistics
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site freeIf Elasticsearch is enabled, this can expose index names and search backend statistics that should normally stay in the admin area.
GET /admin/api/index.php/health-check
This is part of the update and maintenance workflow and can reveal operational state that ordinary users should not be able to inspect.
In other words, the issue is not that guests can reach the backend. The issue is that any ordinary authenticated user can cross the frontend/backend privilege boundary.
I reproduced this against a local Docker deployment of the project.
First, an unauthenticated request to the backend API is rejected:
GET /admin/api/index.php/dashboard/versions HTTP/1.1
Host: 127.0.0.1
Accept: application/json
Response:
HTTP/1.0 401 Unauthorized
Content-Type: application/problem+json
{
"type": "http://127.0.0.1/problems/unauthorized",
"title": "Unauthorized",
"status": 401,
"detail": "Unauthorized access.",
"instance": "/dashboard/versions"
}
Logged in with a normal frontend account:
user1User12345!After login, the same request was sent with the user session cookie:
GET /admin/api/index.php/dashboard/versions HTTP/1.1
Host: 127.0.0.1
Cookie: PHPSESSID=<regular-user-session>
Accept: application/json
Response:
HTTP/1.0 200 OK
Content-Type: application/json
{"success":"Latest version available: phpMyFAQ 4.1.1"}
That is enough to show that a non-admin account can call at least one backend management endpoint successfully.
The main impact is unauthorized access to backend-only operational information.
Depending on which optional features are enabled in a real deployment, this may let a normal user learn:
This was rated as Medium severity.
It was not categorized as High severity because the testing done did not confirm a direct administrative state change through the affected read-oriented endpoints. Still, this is a real privilege separation failure. A frontend account should not be able to query backend admin APIs simply because it has a valid session.
The suggested approach should fix this in two layers.
userIsAuthenticated() with explicit permission checks on backend endpoints that are intended for administrators only.Administration\Api controllers for similar cases and make the access model consistent.403 or 401 where appropriate.