LiveActive security incident?Get immediate response
CVE Record

CVE-2022-38509: Wedding Planner v1.0 was discovered to contain a SQL injection vulnerability via the booking_id parameter a...

Wedding Planner v1.0 was discovered to contain a SQL injection vulnerability via the booking_id parameter at /admin/budget.php.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

CVE-2022-38509 is a SQL injection issue reported in Wedding Planner v1.0. A vulnerable booking identifier can let a remote attacker affect the application database. The CVSS rating is critical because the reported impact includes confidentiality, integrity, and availability loss.

Executive priority

Treat as urgent only where the software is present. The business risk is potential database compromise from a critical SQL injection, but the provided evidence does not show widespread product identification or confirmed active exploitation.

Technical view

The CVE describes CWE-89 SQL injection through the booking_id parameter in /admin/budget.php. The published CVSS 3.1 vector is AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, score 9.8. The source bundle does not provide CPEs or an official vendor patch reference.

Likely exposure

Exposure is likely limited to organizations running Wedding Planner v1.0 or derived deployments containing /admin/budget.php. The source bundle lists affected vendor and product fields as n/a, so asset discovery must rely on application names, code ownership, and deployed route checks.

Exploitation context

A public vulnerability report is cited, and the CVSS vector indicates remote, low-complexity, unauthenticated exploitation. CISA KEV status is false in the bundle, and no cited source confirms active exploitation in the wild.

Researcher notes

The main evidence is the CVE record and a GitHub vulnerability report. Affected metadata is sparse, with no CPEs and n/a vendor/product fields. Validate against local source code and deployments rather than assuming broad commercial exposure.

Mitigation direction

  • Identify and prioritize any Wedding Planner v1.0 deployments.
  • Check the project or vendor source for official guidance or patches.
  • Restrict access to affected admin routes until remediation is verified.
  • If maintaining the code, use parameterized database queries for booking_id handling.
  • Review logs for suspicious access to /admin/budget.php.

Validation and detection

  • Inventory applications named Wedding Planner or derived from that codebase.
  • Confirm whether /admin/budget.php exists in deployed instances.
  • Review booking_id handling for direct SQL string construction.
  • Verify admin route access controls are enforced server-side.
  • Confirm any applied fix prevents SQL injection without breaking budget workflows.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-89: Database access and collection lookup

Injection into data stores can inform collection, data access, and exfiltration detection reviews. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Database behavior lookup

The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2022-38509 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2022-38509Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-89 · source CWE mapping

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.