LiveActive security incident?Get immediate response
CVE Record

CVE-2022-0834: Amelia <= 1.0.46 - Stored Cross Site Scripting via lastName

The Amelia WordPress plugin is vulnerable to Cross-Site Scripting due to insufficient escaping and sanitization of the lastName parameter found in the ~/src/Application/Controller/User/Customer/AddCustomerController.php file which allows attackers to inject arbitrary web scripts onto a pages that executes whenever a user accesses the booking calendar with the date the attacker has injected the malicious payload into. This affects versions up to and including 1.0.46.

HighCVSS 7.2Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2022-0834 is a stored cross-site scripting issue in the Amelia WordPress booking plugin. An attacker could place script content in a customer last name field, and that script may run when someone views the affected booking calendar date.

Executive priority

Prioritize remediation for public WordPress booking sites because this can expose visitors or staff to attacker-controlled browser script. Treat it as high priority where Amelia is internet-facing and outdated.

Technical view

Sources describe insufficient sanitization and escaping of the lastName parameter in Amelia’s AddCustomerController.php. The issue affects Amelia versions up to and including 1.0.46 and is mapped to CWE-79 with CVSS 3.1 score 7.2.

Likely exposure

Exposure is likely limited to WordPress sites running Amelia Booking for Appointments and Events Calendar at version 1.0.46 or earlier, especially where public booking or customer creation workflows are enabled.

Exploitation context

The source bundle does not show CISA KEV listing or other cited evidence of active exploitation. The CVSS vector indicates network reachability, low complexity, no privileges required, changed scope, and limited confidentiality and integrity impact.

Researcher notes

The narrative source states versions up to and including 1.0.46 are affected. The supplied affected-product record appears inconsistent, listing version 0 and defaultStatus unaffected, so validate against Wordfence and CVE records before final scoping.

Mitigation direction

  • Inventory WordPress sites using the Amelia booking plugin.
  • Identify any Amelia installations at version 1.0.46 or earlier.
  • Check vendor or Wordfence guidance for the fixed release before changing production.
  • Update Amelia to a vendor-supported fixed version when confirmed.
  • If no fix is available, assess temporarily disabling exposed booking workflows.

Validation and detection

  • Confirm the installed Amelia plugin version from WordPress administration or asset inventory.
  • Review booking calendar pages for unexpected script execution or altered customer names.
  • Inspect customer records for suspicious lastName values containing markup or script-like content.
  • Check web and WordPress logs for unusual booking or customer creation activity.
Prepared
Confidence
medium
Sources
4

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-0834 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
High
CVSS
7.2 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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
3Source 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
7.2CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N3.92.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.2High
CVSS 3.1 vector shape for CVE-2022-0834Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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
ameliabookingBooking for Appointments and Events Calendar – Amelia0unaffected
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.