Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-76876 – Unauthenticated Sensitive Credential Disclosure – Craftplan < 0.5.1

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

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-76876 is a broken access control vulnerability in Craftplan (puemos/craftplan) affecting all versions prior to 0.5.1. The flaw allows unauthenticated attackers to retrieve decrypted SMTP passwords, email API keys, and email API secrets via the Settings API. The issue has been rated High severity (CVSS 8.2).

Technical details

  • Root cause: The Settings API resource enforced an "always-allow" authorization policy that bypassed identity verification entirely, instead of restricting access to authenticated staff/administrators.
  • Trigger conditions: An attacker sends a direct GET request to the Settings JSON:API endpoint with a valid record identifier — no authentication or session token is required.
  • Attack vector: Network — the vulnerable API is reachable remotely, requiring no user interaction and no prior privileges.
  • Impact: Disclosure of decrypted SMTP credentials, email API keys, and email API secrets stored in the application’s settings, which could allow an attacker to hijack outbound email infrastructure, send spoofed communications, or pivot to connected email/SMTP provider accounts.
  • Weakness classification: CWE-862 (Missing Authorization).

Affected software

  • Craftplan (puemos/craftplan) — all versions prior to 0.5.1

Severity

  • CVSS v4.0 Base Score: 8.2 (High) — CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
  • CVSS v3.1 Base Score: 5.9 (Medium) — CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

Mitigation and recommended actions

  • Immediate: Upgrade Craftplan to version 0.5.1 or later, which restricts Settings JSON:API reads to authorized staff and administrators and prevents SMTP and email-provider credentials from being serialized in API responses.
  • If immediate patching is not possible:
    • Restrict network access to the Craftplan Settings API endpoint to trusted internal sources only (e.g., via firewall rules or reverse proxy access controls).
    • Rotate any SMTP passwords, email API keys, and email API secrets stored in Craftplan settings, since these may already have been exposed.
    • Monitor logs for unauthenticated requests to Settings API endpoints as an indicator of exploitation attempts.

References

Are you exposed?

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

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

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

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

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

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge