VulnTitan VulnTitan Security command center
Plugin Vulnerability Hub
Plugin 3 known issues Latest disclosed Feb 14, 2025

CodeBard Help Desk Vulnerabilities

Review known vulnerability records for the WordPress plugin CodeBard Help Desk (`codebard-help-desk`), including severity, CVE references, affected versions, and patch status.

Recent tracked CVEs on this page include CVE-2025-22757, CVE-2025-22760 and CVE-2024-56222, so operators can jump from disclosure to patch validation without scanning the full feed first.

View on WordPress.org Back to Feed
Known Records
3
High or Critical
0
Patch Coverage
100%
Last Updated
Feb 24, 2025
Related Security Guides

Use these guides while reviewing CodeBard Help Desk 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 CodeBard Help Desk 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
3
1. Match the Package
Confirm the installed WordPress plugin slug is codebard-help-desk 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
3 records 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-2025-22757 Medium
Stored Cross-Site Scripting remediation for CodeBard Help Desk

Affected range: Versions up to 1.1.2. Fixed version is not listed yet.

CVE-2025-22760 Medium
Cross-Site Scripting remediation for CodeBard Help Desk

Affected range: Versions up to 1.1.2. Fixed version is not listed yet.

CVE-2024-56222 Medium
Cross-Site Request Forgery remediation for CodeBard Help Desk

Affected range: Versions up to 1.1.1. Fixed version: 1.1.2.

Priority CVE Quick Links

Fast paths into CodeBard Help Desk CVE reports

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

Indexed CVEs
3
Tracked CVE Issue Type Affected Versions Fixed Version CVSS
CVE-2025-22757
CodeBard Help Desk <= 1.1.2 - Authenticated (Subscriber+) Stored Cross-Site Scriptin...
 Stored Cross-Site Scripting Versions up to 1.1.2 No patch listed CVSS 6.4
CVE-2025-22760
CodeBard Help Desk <= 1.1.2 - Reflected Cross-Site Scripting
 Cross-Site Scripting Versions up to 1.1.2 No patch listed CVSS 6.1
CVE-2024-56222
CodeBard Help Desk <= 1.1.1 - Cross-Site Request Forgery
 Cross-Site Request Forgery Versions up to 1.1.1 1.1.2 CVSS 4.3
CVE-2025-22757 Medium No patch listed
CVE-2025-22757 CodeBard Help Desk Stored Cross-Site Scripting

CodeBard Help Desk <= 1.1.2 - Authenticated (Subscriber+) Stored Cross-Site Scripting

CVE-2025-22760 Medium No patch listed
CVE-2025-22760 CodeBard Help Desk Cross-Site Scripting

CodeBard Help Desk <= 1.1.2 - Reflected Cross-Site Scripting

CVE-2024-56222 Medium 1.1.2
CVE-2024-56222 CodeBard Help Desk Cross-Site Request Forgery

CodeBard Help Desk <= 1.1.1 - Cross-Site Request Forgery

Coverage Snapshot

What this page helps you verify fast

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

Patch Visibility
3 records 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-2025-22757, CVE-2025-22760 and CVE-2024-56222
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 CodeBard Help Desk

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

Plugin Medium Patched: No CVE-2025-22757
CVE-2025-22757: CodeBard Help Desk <= 1.1.2 - Authenticated (Subscriber+) Stored Cross-Site Scripting

The CodeBard Help Desk plugin for WordPress is vulnerable to Stored Cross-Site Scripting in all versions up to, and including, 1.1.2 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Subscriber-level access and ab...

Published
Feb 14, 2025
Patched Release
Not published
Affected Versions
Versions up to 1.1.2
Next Step
Open the full report for remediation notes and references.
Review CVE-2025-22757 fixed version details Open CVE Reference
Plugin Medium Patched: No CVE-2025-22760
CVE-2025-22760: CodeBard Help Desk <= 1.1.2 - Reflected Cross-Site Scripting

The CodeBard Help Desk plugin for WordPress is vulnerable to Reflected Cross-Site Scripting in versions up to, and including, 1.1.2 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in...

Published
Jan 14, 2025
Patched Release
Not published
Affected Versions
Versions up to 1.1.2
Next Step
Open the full report for remediation notes and references.
Review CVE-2025-22760 fixed version details Open CVE Reference
Plugin Medium Patched: Yes CVE-2024-56222
CVE-2024-56222: CodeBard Help Desk <= 1.1.1 - Cross-Site Request Forgery

The CodeBard Help Desk plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 1.1.1. This is due to missing or incorrect nonce validation on the close_ticket_p() function. This makes it possible for unauthenticated attackers to close ti...

Published
Dec 19, 2024
Patched Release
1.1.2
Affected Versions
Versions up to 1.1.1
Next Step
Update to 1.1.2 or newer if supported.
Review CVE-2024-56222 fixed version details Open CVE Reference