CVE-2014-8675

Public exploit available. Not confirmed exploited in the wild yet. No fix published yet.

CVSS 3.07.5High EPSS percentile96th13% chance in 30 days CISA KEVNot listedNo confirmed exploitation
Public exploit: 2 sources FixNone yetNo fix or workaround published

Published 2017-08-31Updated 2026-05-13Sources: CVE.org, NVD

NVD CVE.org

What to do

No fixed build or workaround is published yet. Limit exposure and watch for a patch.

SoplanningAffected: ≤ 1.32Upgrade to: after 1.32Stated by: NVD

Versions as the sources state them. Full version matrix after sign-in

Steps

Written by AI from the record

Check whether you run Soplanning 1.32 or earlier and whether shared ICAL calendar links have been generated.
Disable or replace existing shared ICAL links until your software vendor confirms a safe remediation.
No fixed Soplanning version is currently identified; ask the vendor for a supported upgrade or replacement path.
Change passwords for calendar owners whose links may have been shared, especially reused passwords.

May need vendor or contractor work

Check it yourselfA free OpenVAS check exists for this CVE. Run it against your hosts.Is your organisation exposed?Request an assessment to establish which checks fit your systems.

What it is

From the CVE record

Soplanning 1.32 and earlier generates static links for sharing ICAL calendars with embedded login information, which allows remote attackers to obtain a calendar owner's password via a brute-force attack on the embedded password hash.

In plain language

Written by AI from the record

Soplanning 1.32 or earlier can expose calendar owners’ passwords through shared calendar links, so small businesses using those versions should act.

Unauthenticated network-based credential disclosure in Soplanning’s static ICAL sharing links enables offline brute-forcing of an embedded encrypted password.

If you're affected

Calendar account takeover
Schedule data exposure
Unauthorized calendar access

What is it

Soplanning created calendar-sharing links that included information attackers can use to work out the calendar owner’s password. It is like leaving a locked key box outside your office with a code that can be tried repeatedly until it opens.

Who is affected

This matters to you if you run Soplanning 1.32 or earlier and use its shared ICAL calendar links. It is a risk only when those links have been generated and are available to an attacker.

How urgent is it

Public exploit code is available, making this practical for attackers to test against exposed shared links. Treat this as an amber priority: remove or replace the sharing links and rotate potentially exposed passwords promptly, but there is no confirmed active exploitation in the findings.

What to do — in detail

Confirm the installed Soplanning version and inventory all static ICAL sharing links, including links sent by email, placed on websites, or stored in third-party calendar applications. Systems running version 1.32 or earlier with generated sharing links are affected.

No vendor fixed version or patch is identified in the findings. If an upgrade path is available from the vendor, validate it in a test environment before deployment; otherwise, disable ICAL sharing links and use an alternative sharing method that does not place credential-derived data in a static URL.

If patching or replacement is delayed, revoke existing shared links where possible, prevent public access to them, and reset passwords for affected calendar owners. Review web-server and application access logs for requests to shared calendar URLs and unusual repeated access patterns. This CVE is not listed in CISA KEV, so no CISA remediation due date applies.

Technical context

CVE-2014-8675 is rated CVSS 7.5 High and is associated with CWE-200 information exposure. It is remotely reachable over the network, requires no authentication or user interaction, and applies when Soplanning 1.32 or earlier has generated static ICAL sharing links. The links contain an encrypted password value that can be brute-forced to recover credentials. Two public exploits are known. EPSS predicts a 12.5% likelihood (96th percentile) and is falling; this is predictive only, and the findings do not confirm exploitation in the wild. The CVE is not in CISA KEV.

This is a general assessment based on public vulnerability data. It does not account for your specific infrastructure — when in doubt, consult a security specialist.

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS96th

Public exploit

CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

2 sources with a proof of concept or module.

Exploit links, PoCs and Metasploit modules after sign-in

EPSS

13% chance of exploitation activity in the next 30 days, which ranks it in the 96th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

23 events over 3309 days, from the signal feeds we watch.

2026-09-22EPSS band changelow → moderateepss band change
2026-09-21EPSS band changemoderate → lowepss band change
2026-09-06EPSS band change0 → moderateepss band change
2026-09-05EPSS band changemoderate → 0epss band change
2026-08-31EPSS band change0 → moderateepss band change
2026-08-29EPSS band changemoderate → low

Affected products

soplanningcommercial
- soplanningOn-premConsumer Software / productivity

And 1 more affected product. See all after sign-in

Technical detail

CVSS 3.0 vector

Open in the CVSS calculator

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Scored 7.5 by NVD.

How it is reached

Attack Vector NetworkExploitable remotely over the network without any special conditions
Attack Complexity LowNo special conditions — the attack can be reliably reproduced
Privileges Required NoneNo authentication required — anyone can exploit this
User Interaction NoneNo user interaction needed — fully automated exploitation

Scope

Scope UnchangedImpact is limited to the vulnerable component itself

Impact if exploited

Confidentiality HighTotal information disclosure — all data in the component is compromised
Integrity NoneNo integrity impact
Availability NoneNo availability impact