CVE-2022-38509: n/a
Source CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 1.0% chance of exploitation in 30 days – higher than 62% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 19 Sep 2022
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.
What to do
AI-suggested
European organizations should immediately assess whether Wedding Planner v1.0 is deployed within their environment, particularly versions without patches addressing this vulnerability. Since no official patches are currently available, organizations should implement compensating controls such as: 1) Restricting access to the /admin/budget.php endpoint through network segmentation, VPNs, or IP whitelisting to limit exposure to trusted users only. 2) Employing Web Application Firewalls (WAFs) with rules specifically designed to detect and block SQL injection attempts targeting the booking_id parameter. 3) Conducting thorough input validation and parameterized query implementation in the application code to prevent injection vectors, if source code access and development resources are available. 4) Monitoring logs for unusual database query patterns or repeated access attempts to the vulnerable endpoint. 5) Planning for an urgent upgrade or migration to a patched or alternative wedding planning solution that addresses this vulnerability. 6) Educating administrative users on the risks and signs of compromise to enable early detection and response. These measures should be combined to reduce attack surface and mitigate risk until a formal patch is released.
Description
Wedding Planner v1.0 was discovered to contain a SQL injection vulnerability via the booking_id parameter at /admin/budget.php.