Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2018-18923: AbiSoft Ticketly 1.0 is affected by multiple SQL Injection vulnerabilities through the parameters name, catego

66
This week
CRITICAL 9.8REMOTEDOWNGRADE

CVE-2018-18923 is a critical-severity flaw (CVSS 9.8) affecting ticketly. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

AbiSoft Ticketly 1.0 is affected by multiple SQL Injection vulnerabilities through the parameters name, category_id and description in action/addproject.php; kind_id, priority_id, project_id, status_id and title in action/addticket.php; and kind_id and status_id in reports.php.

Why this priority

  • Critical severity
  • Public exploit reference
  • Remotely exploitable, no login, no user action

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score9.8 (Critical)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededNone
User interactionNone
EPSS exploit chance3.2% (top 12%)
CISA exploited listNo
WeaknessCWE-89
Published2018-12-13
Last modified2026-06-17
Publisher (CNA): MITRE · Vendor: abisoftgt

Share: LinkedIn · X · Reddit

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

abisoftgt ticketly DOWNGRADE
Affected: 1.0
Fixed in: no fixed release known
Safe to downgrade to: a release before 1.0
1. Check installed version
apt-cache policy ticketly || rpm -q ticketly || ticketly --version
2. No fixed release: DOWNGRADE to a release before 1.0 (Debian / Ubuntu)
apt-cache madison ticketly sudo apt install ticketly=<VERSION_BEFORE_1.0> sudo apt-mark hold ticketly
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list ticketly sudo dnf downgrade ticketly-<VERSION_BEFORE_1.0> sudo dnf versionlock add ticketly
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.

Public exploits and detection

Public code exists for this CVE. Treat unpatched systems as at risk, and only run PoCs in a lab.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2018-18923?

ticketly: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2018-18923 being exploited?

CVE-2018-18923 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2018-18923 affect?

CVE-2018-18923 affects ticketly. Severity is critical (CVSS 9.8). AbiSoft Ticketly 1.0 is affected by multiple SQL Injection vulnerabilities through the parameters name, category_id and description in action/addproject.php; kind_id, priority_id, project_id, status_id and title in action/addticket.php; and

How urgent is CVE-2018-18923?

Priority 66/100. Critical severity; Public exploit reference; Remotely exploitable, no login, no user action

Software pages

PHP vulnerabilities

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.