PHP2Shell : See if you’re affected with a free external attack surface scan. Click Here > 

New CVE Detected

CVE-2026-91078 – Unauthenticated Privileged Account Takeover – TillKit WordPress Plugin < 1.0.5

Be the first to know when new zero-days emerge:

Summary

CVE-2026-91078 is an Improper Authentication (CWE-287) vulnerability in the TillKit WordPress plugin, affecting all versions prior to 1.0.5. The plugin provisions a privileged Point-of-Sale (POS) "manager" account at activation time with a hard-coded, publicly known default PIN that site owners are never required to change. Because the public-facing POS login endpoint validates access solely on this static PIN with no identity or capability checks, any unauthenticated remote attacker can log in as the privileged POS account. The issue carries a CVSS v3.1 base score of 8.2 (High).

Technical details

  • Root cause: On activation, TillKit automatically creates a privileged POS/manager account and assigns it a hard-coded PIN value that is publicly known (present in the plugin code), rather than generating a unique secret or forcing a mandatory change on first use.
  • Trigger conditions: The vulnerable configuration exists on any site running TillKit < 1.0.5 where the default manager PIN has not been manually changed after installation — the default, out-of-the-box state.
  • Attack vector: The plugin’s public POS login endpoint is reachable without authentication and accepts the default PIN as the sole credential, with no additional identity verification, rate limiting reference, or capability check described in the advisory.
  • Impact: A remote, unauthenticated attacker who supplies the known default PIN obtains a privileged POS session, enabling them to read customer and site-user personal data and to modify store/POS data (confidentiality and integrity impact; no direct availability impact per the CVSS vector).

Affected software

  • TillKit WordPress plugin — all versions prior to 1.0.5
  • Fixed in: TillKit 1.0.5

Severity

  • CVSS v3.1 Base Score: 8.2 (High)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N

Mitigation and recommended actions

  • Immediate: Update the TillKit plugin to version 1.0.5 or later, where the default PIN requirement has been addressed.
  • If immediate patching is not possible:
    • Manually change the default POS manager PIN to a strong, unique value immediately — do not rely on default credentials.
    • Restrict or disable access to the public POS login endpoint at the network or web server layer (e.g., IP allow-listing) until the plugin can be updated.
    • Audit POS account activity and customer/user data for signs of unauthorized access if the default PIN may have been exposed.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge