LiveActive security incident?Get immediate response
CVE Record

CVE-2023-6751: Hostinger <= 1.9.7 - Missing Authorization to Maintenance Mode Activation

The Hostinger plugin for WordPress is vulnerable to unauthorized plugin settings update due to a missing capability check on the function publish_website in all versions up to, and including, 1.9.7. This makes it possible for unauthenticated attackers to enable and disable maintenance mode.

HighCVSS 7.3Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2023-6751 lets an unauthenticated attacker toggle maintenance mode in the Hostinger WordPress plugin through a missing authorization check. Business impact is mainly website disruption and unauthorized settings changes, with limited confidentiality and integrity impact reflected in the CVSS score.

Executive priority

Prioritize remediation for public WordPress sites because the bug can be used without login and can disrupt site availability. It is not proven actively exploited in the supplied evidence, but the ease of abuse justifies near-term patching or disabling on exposed sites.

Technical view

The issue is CWE-862 in the publish_website function of Hostinger Tools for WordPress, affecting versions up to and including 1.9.7. The vulnerable path lacks a capability check, allowing unauthenticated maintenance mode enablement or disablement. CVSS 3.1 is 7.3, network-accessible, low complexity, no privileges, no user interaction.

Likely exposure

Exposure is limited to WordPress sites running the Hostinger plugin or Hostinger Tools at version 1.9.7 or earlier. The bundle does not establish exposure for unrelated Hostinger services or non-WordPress products.

Exploitation context

The CVE is not listed as CISA KEV in the bundle, and no provided source states active exploitation. The issue is remotely reachable and unauthenticated, so internet-facing WordPress sites using the affected plugin should be treated as plausible targets.

Researcher notes

Evidence supports missing authorization on publish_website and unauthorized maintenance mode toggling. The supplied affected metadata is inconsistent, showing product Hostinger Tools with version 0 while the description and title state versions through 1.9.7. Treat exact product naming as needing vendor confirmation.

Mitigation direction

  • Inventory WordPress sites for Hostinger Tools or the Hostinger plugin.
  • Upgrade affected installations to a vendor-confirmed version newer than 1.9.7.
  • If no confirmed fix is available, follow Hostinger and WordPress plugin guidance.
  • Disable the plugin where business impact allows until remediation is confirmed.
  • Review maintenance mode settings after remediation.

Validation and detection

  • Confirm installed plugin names and versions across all WordPress environments.
  • Flag any Hostinger plugin or Hostinger Tools version 1.9.7 or earlier.
  • Check whether maintenance mode was unexpectedly enabled or disabled.
  • Review WordPress and web logs for suspicious unauthenticated settings changes.
  • Verify anonymous users cannot modify plugin maintenance settings after remediation.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-862: Authorization and privilege behavior lookup

Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2023-6751 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.3CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L3.93.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.3High
CVSS 3.1 vector shape for CVE-2023-6751Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
hostingerHostinger Tools0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-862 · source CWE mapping

Missing Authorization

Missing Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.