LiveActive security incident?Get immediate response
CVE Record

CVE-2022-40484: Wedding Planner v1.0 was discovered to contain a SQL injection vulnerability via the booking parameter at /...

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

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

Wedding Planner v1.0 has a critical SQL injection issue in an admin client-editing page. If reachable, an unauthenticated attacker may be able to affect database confidentiality, integrity, and availability. The source bundle does not identify a vendor CPE, official patch, or confirmed exploitation.

Executive priority

Treat as urgent for any confirmed deployment because the reported issue could compromise business data. Prioritize discovery first, since source metadata is incomplete and may not map cleanly through standard CPE-based scanners.

Technical view

CVE-2022-40484 is a CWE-89 SQL injection in the booking parameter of /admin/client_edit.php in Wedding Planner v1.0. CVSS 3.1 is 9.8, with network access, low complexity, no privileges, and no user interaction. Vendor and product metadata are incomplete in the CVE source data.

Likely exposure

Exposure is likely limited to organizations running Wedding Planner v1.0 with /admin/client_edit.php reachable, especially internet-facing deployments. The CVE data lacks CPEs and vendor identifiers, so asset matching may require application-name and codebase inventory checks.

Exploitation context

The bundle does not show CISA KEV listing or cited evidence of active exploitation. The referenced report describes SQL injection in a specific parameter, but no official exploit-status confirmation, patch advisory, or mitigation notice is included.

Researcher notes

Evidence supports a critical SQL injection finding in Wedding Planner v1.0. Confidence is limited by sparse vendor metadata, no CPEs, no official patch information, and no KEV status. Avoid assuming broader product families or exploitation activity without additional sources.

Mitigation direction

  • Identify any Wedding Planner v1.0 deployments and owners.
  • Check project or vendor guidance for a patched release or official fix.
  • Restrict access to the admin application while remediation is assessed.
  • Retire or replace unsupported deployments if no maintained fix exists.
  • Review application database access controls for least privilege.

Validation and detection

  • Search asset inventory for Wedding Planner v1.0 instances.
  • Confirm whether /admin/client_edit.php is externally reachable.
  • Review application logs for suspicious booking parameter activity.
  • Verify whether any deployed code includes an official or reviewed fix.
  • Document compensating controls if immediate removal is not possible.
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-40484 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-40484Attack 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.