Administrative Interface Publicly Accessible

An administrative interface can be reached from the internet, so anyone can attempt to sign in to it or attack weaknesses in it.

SeverityMedium
CVSS 3.14.8 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N Open in the calculator
CVSS 4.06.3 CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N Open in the calculator
CWECWE-668: Exposure of Resource to Wrong Sphere
OWASP Top 10A01:2025 Broken Access Control
MITRE ATT&CKT1110 Brute Force, T1190 Exploit Public-Facing Application
CategorySecurity Misconfiguration

Description

An administrative interface is reachable from the internet rather than only from a management network. Examples include content management system back ends such as /wp-admin and /administrator, the application's own administration area, application server consoles such as the Apache Tomcat Manager, database tools such as phpMyAdmin and Adminer, hosting control panels, and monitoring or build tools such as Grafana, Kibana and Jenkins.

The interface may require authentication, but its exposure still allows anyone to attempt to sign in, to try passwords at scale through password guessing, password spraying and credential stuffing, and to exploit any published or undiscovered vulnerability in the administrative software, which is often complex, highly privileged and less hardened than the public application, without first gaining a foothold elsewhere. Access to an administrative interface usually gives control of the application and its data, and often code execution on the server, for example by deploying a web application archive through the Tomcat Manager or by editing plugins in a content management system.

The risk is lower where multi-factor authentication, strong passwords, rate limiting and prompt patching are in place, and higher where any of them is missing. Where no authentication is required at all, or default credentials are accepted, that is a more serious issue reported in its own right.

Exposed interfaces are found by content discovery against common administrative paths, by enumerating subdomains and alternative ports, and through search engines and certificate transparency logs, which attackers use in the same way.

Remediation

Make the administrative interface reachable only from trusted networks, and protect the accounts that use it:

  • Restrict access at the firewall, reverse proxy or web server to a management network, a VPN or a zero trust access service, and refuse it from everywhere else.
  • Where possible, host administrative functions on a separate host name or port that is not published to the internet, so that network controls can apply to them as a whole.
  • Require multi-factor authentication for every administrative account.
  • Enforce strong, unique passwords, limit the rate of sign-in attempts, and alert on repeated failures.
  • Keep the administrative software patched, and remove administrative components that are not used.
# nginx: management network only (documentation range shown) location /admin/ { allow 192.0.2.0/24; deny all; } # Apache <Location "/admin/"> Require ip 192.0.2.0/24 </Location>

As an interim measure while network restrictions are arranged, enable multi-factor authentication and rate limiting. Confirm the fix by requesting the interface from an untrusted network: it should be refused or unreachable.

References


Add This Finding to Your Library

In Pental this write-up is in Settings, Library. Add to my library copies it into your own, rated in your firm's CVSS version, ready to put in your own words.

Free trial  ·  No card required

Only need the reporting? Our reporting tool is free and open source, with the same library.


More Web Applications Findings

Every Web Applications finding