← Back to results
Vulnerability record · public intelligence
CVE-2015-10099
MEDIUM

CP Appointment Calendar Plugin dex_appointments.php dex_process_ready_to_go_appointment sql injection

Published Apr 10, 2023 · Updated Nov 3, 2026

Severity · CVSSMEDIUM · Not scored
Known exploitationNot listed
EPSS / likelihood1.03%
QFinch risk scoreNot available

Original summary

Normalized public record · Updated Nov 3, 2026

CP Appointment Calendar Plugin dex_appointments.php dex_process_ready_to_go_appointment sql injection

Publisher and source text is retained separately from QFinch interpretation.

QFinch assessment

A vulnerability classified as critical has been found in CP Appointment Calendar Plugin up to 1.1.5 on WordPress. This affects the function dex_process_ready_to_go_appointment of the file dex_appointments.php. The manipulation of the argument itemnumber leads to sql injection. It is possible to initiate the attack remotely. The patch is named e29a9cdbcb0f37d887dd302a05b9e8bf213da01d. It is recommended to apply a patch to fix this issue. The associated identifier of this vulnerability is VDB-225351.

Evidence: public source records

Affected products

Affected scope reported by the available public evidence
Affected package, product or rangeFix status
Consult the referenced vendor advisory for affected versions.Consult source advisory

Matching a version is only one part of assessing exposure. QFinch has not assessed your environment on this public page.

Remediation

Apply the vendor-supported fixed release or mitigation, then verify the affected component is no longer reachable.

  1. Confirm the affected product and reachable code path exist in your environment.
  2. Apply the vendor-supported patch or mitigation from the primary advisory.
  3. Rescan the exact deployed revision and retain verification evidence.
Review primary references

Evidence coverage

FIRST-EPSSCVE-LIST-V5
SSVC priority
LOW
Confidence
Not available
Aliases
None reported

Scores appear only when corresponding evidence exists. Missing data is never interpreted as zero risk.

Sources and record history

  1. vuldb.com ↗
  2. vuldb.com ↗
  3. Patch commit ↗

Record history

Published Apr 10, 2023 · Last refreshed Nov 3, 2026