VulnTitan VulnTitan Security command center
Plugin Vulnerability Hub
Plugin 1 known issue Latest disclosed Jun 05, 2026

Klamra Paycal for Aspaclaria Vulnerabilities

Review known vulnerability records for the WordPress plugin Klamra Paycal for Aspaclaria (`klamra-paycal-for-aspaclaria`), including severity, CVE references, affected versions, and patch status.

Recent tracked CVEs on this page include CVE-2026-8611, so operators can jump from disclosure to patch validation without scanning the full feed first.

View on WordPress.org Back to Feed
Known Records
1
High or Critical
0
Patch Coverage
100%
Last Updated
Jun 05, 2026
Related Security Guides

Use these guides while reviewing Klamra Paycal for Aspaclaria fixes

Pair this plugin vulnerability hub with practical WordPress hardening, scanner, and patch workflow guidance.

Hardening
WordPress hardening checklist for exposed plugins

Review patch cadence, privileged access, XML-RPC exposure, backups, and monitoring controls.
Plugin Security
WordPress plugin security basics for patch decisions

Use ownership, update testing, least privilege, and removal criteria to reduce plugin risk.
Scanning
WordPress vulnerability scanner buyer's guide

Compare scanner coverage for plugin CVEs, version detection, alert noise, and remediation workflow.
Patch Decision Workflow

How to prioritize Klamra Paycal for Aspaclaria remediation

Use the hub as a decision layer before opening individual records: confirm whether the issue has a CVE, whether a fixed version exists, and whether the affected range overlaps production installs.

Search-Ready Records
1
1. Match the Package
Confirm the installed WordPress plugin slug is klamra-paycal-for-aspaclaria before acting on any CVE from this cluster.
2. Sort by Severity
Start with 0 high or critical records, then review medium and unrated findings with public references.
3. Check Patch Evidence
1 record include a patch path; verify compatibility before closing the finding.
4. Monitor Gaps
0 records still lack a listed fixed release, so keep this hub in the review queue.
High-Signal Remediation Targets
CVE-2026-8611 Medium
Sensitive Information Exposure remediation for Klamra Paycal for Aspaclaria

Affected range: Versions up to 1.1.4. Fixed version: 1.1.5.

Priority CVE Quick Links

Fast paths into Klamra Paycal for Aspaclaria CVE reports

Start with the highest-signal CVE records for this WordPress plugin before scanning the full vulnerability feed.

Indexed CVEs
1
Tracked CVE Issue Type Affected Versions Fixed Version CVSS
CVE-2026-8611
Klamra Paycal for Aspaclaria <= 1.1.4 - Insecure Direct Object Reference to Authenti...
 Sensitive Information Exposure Versions up to 1.1.4 1.1.5 CVSS 4.3
CVE-2026-8611 Medium 1.1.5
CVE-2026-8611 Klamra Paycal for Aspaclaria Sensitive Information Exposure

Klamra Paycal for Aspaclaria <= 1.1.4 - Insecure Direct Object Reference to Authenticated (Subscriber+) Sensitive Information Exposure via 'invoice_id' Parameter

Coverage Snapshot

What this page helps you verify fast

This hub clusters tracked records for Klamra Paycal for Aspaclaria so operators can confirm whether a disclosed issue maps to the installed slug, version range, and patch path.

Patch Visibility
1 record include a published patch path, leaving 0 with no listed safe release yet.
Severity Mix
0 critical and 0 high severity findings.
Recent CVEs
CVE-2026-8611
Reference Workflow
Jump from the hub into the full report when you need remediation notes, exploit context, CVSS vectors, or source references.
Triage First

Open the records most likely to drive action

These recent records surface the CVE strings, patch cues, and direct report links most operators need first.

Known Vulnerabilities

Reports for Klamra Paycal for Aspaclaria

Sorted by latest disclosure date so newly published issues surface first.

Plugin Medium Patched: Yes CVE-2026-8611
CVE-2026-8611: Klamra Paycal for Aspaclaria <= 1.1.4 - Insecure Direct Object Reference to Authenticated (Subscriber+) Sensitive Information Exposure via 'invoice_id' Parameter

The Klamra Paycal for Aspaclaria plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 1.1.4 via the 'invoice_id' parameter due to missing validation on a user controlled key. This makes it possible for authenticated attacker...

Published
Jun 05, 2026
Patched Release
1.1.5
Affected Versions
Versions up to 1.1.4
Next Step
Update to 1.1.5 or newer if supported.
Review CVE-2026-8611 fixed version details Open CVE Reference