LiveActive security incident?Get immediate response
CVE Record

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

Wedding Planner v1.0 was discovered to contain a SQL injection vulnerability via the id parameter at /package_detail.php.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

This CVE describes a critical SQL injection in Wedding Planner v1.0. An unauthenticated remote attacker could potentially manipulate database queries through the package detail identifier, risking data theft, data changes, or service disruption. The sources do not identify a vendor patch or confirm real-world exploitation.

Executive priority

Treat this as urgent for any public deployment because the potential business impact includes customer data exposure, unauthorized data modification, and outage. Priority drops if the application is not deployed, not reachable, or the affected code is absent.

Technical view

CVE-2022-40485 is a CWE-89 SQL injection in Wedding Planner v1.0 affecting the id parameter in /package_detail.php. The CVSS 3.1 score is 9.8 because the issue is network-reachable, low complexity, requires no privileges or user interaction, and can impact confidentiality, integrity, and availability.

Likely exposure

Exposure is most likely for internet-facing deployments of Wedding Planner v1.0 or reused code from that project. The CVE metadata lists vendor and product as n/a, so asset identification may require application fingerprinting and code review.

Exploitation context

The CVE is not listed as CISA KEV in the supplied bundle. The public reference is a bug report, but the provided sources do not prove active exploitation, widespread scanning, or available vendor remediation.

Researcher notes

Evidence is narrow: one CVE record and one public bug report identify the vulnerable parameter and file. Affected vendor metadata is incomplete, and no patch level is provided. Focus validation on confirming the exact application and vulnerable code path before declaring exposure.

Mitigation direction

  • Identify any Wedding Planner v1.0 deployments or copied package detail code.
  • Check maintainer or vendor guidance before relying on a local fix.
  • Restrict public access to affected pages until remediation is confirmed.
  • Have developers replace unsafe SQL construction with parameterized database queries.
  • Add server-side validation for package identifiers and reject unexpected input.
  • Back up and review database integrity if exposure was public.

Validation and detection

  • Inventory web applications for Wedding Planner v1.0 or matching package detail functionality.
  • Review package detail code for unsafe use of the id parameter in SQL queries.
  • Check application logs for suspicious requests to package_detail.php.
  • Confirm database queries use prepared statements or equivalent safe APIs.
  • Run regression tests covering normal and invalid package identifier handling.
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-40485 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-40485Attack 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.