LiveActive security incident?Get immediate response
CVE Record

CVE-2022-43084: A cross-site scripting (XSS) vulnerability in admin-add-vehicle.php of Vehicle Booking System v1.0 allows a...

A cross-site scripting (XSS) vulnerability in admin-add-vehicle.php of Vehicle Booking System v1.0 allows attackers to execute arbitrary web scripts or HTML via a crafted payload injected into the v_name parameter.

MediumCVSS 4.8Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This CVE describes a stored or reflected cross-site scripting risk in Vehicle Booking System v1.0. A high-privilege user path can accept unsafe content in the vehicle name field, potentially causing script or HTML to run in another user's browser. Business impact is limited but relevant where admin access or trust boundaries are weak.

Executive priority

Treat this as a moderate-priority web application issue. It is unlikely to be internet-scale urgent from the supplied evidence, but it can affect administrator trust, session safety, and content integrity where the vulnerable application is in use.

Technical view

CVE-2022-43084 is CWE-79 XSS in admin-add-vehicle.php through the v_name parameter. CVSS 3.1 is 4.8: network reachable, low complexity, high privileges required, user interaction required, changed scope, low confidentiality and integrity impact, no availability impact.

Likely exposure

Exposure appears limited to deployments of Vehicle Booking System v1.0 using the admin vehicle-add workflow. The CVE affected-product metadata is listed as n/a, so exact vendor, package identity, and version range are incomplete in the supplied sources.

Exploitation context

The source bundle does not show CISA KEV listing or other evidence of active exploitation. The CVSS vector indicates an attacker needs high privileges and a victim interaction, making this more likely in compromised-admin, malicious-insider, or shared-administration scenarios.

Researcher notes

Evidence is narrow: the CVE description and one public GitHub reference identify the vulnerable file and parameter, but affected vendor metadata and official remediation are not provided. Avoid broad product assumptions until deployment inventory and upstream guidance are confirmed.

Mitigation direction

  • Check the project or vendor for official security guidance or updates.
  • Restrict access to the admin vehicle-management interface.
  • Validate and encode vehicle name values before storing or rendering.
  • Review existing vehicle records for suspicious script or HTML content.
  • Prioritize remediation where multiple administrators use the same system.

Validation and detection

  • Confirm whether Vehicle Booking System v1.0 is deployed.
  • Identify whether admin-add-vehicle.php is reachable in production.
  • Review handling of the v_name parameter in a non-production environment.
  • Check rendered vehicle names for unsafe HTML execution risk.
  • Inspect administrative records and logs for suspicious vehicle-name entries.
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-79: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. 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
cve · low confidence lookup

CVE-2022-43084 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
Medium
CVSS
4.8 (3.1)
Known Exploited
No
Published

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

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
4.8CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N1.72.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

4.8Medium
CVSS 3.1 vector shape for CVE-2022-43084Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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-79 · source CWE mapping

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.