CVE-2022-22791
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedSYNEL - eharmony Authenticated Blind & Stored XSS. Inject JS code into the "comments" field could lead to potential stealing of cookies, loading of HTML tags and JS code onto the system.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceA stored XSS vulnerability in SYNEL eharmony allows authenticated users to inject malicious JavaScript code into the comments field. This stored payload executes when other users view the affected content, enabling cookie theft and arbitrary HTML/JS execution in victims' browsers.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 8.0.2.3CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Synel Eharmony installed versionLocate the version information for your Synel Eharmony installation through the software's about page, system information panel, or version file in the installation directoryAffected if The installed version is 8.0.2.3 exactly, as this is the only version confirmed affected by this CVE
-
Confirm comments feature is accessibleLog into the application as an authenticated user and navigate to areas where comments can be submitted (such as user profiles, content pages, or communication modules where the comments field exists)Affected if The comments input field is present and functional in the application interface, making the stored XSS attack surface available
-
Inspect stored comments for suspicious contentQuery the database table storing comments (or use the admin panel if available) to examine existing comment entries for unexpected script tags, javascript: URIs, or event handler attributesAffected if Any stored comments contain HTML script elements, img/onerror patterns, or other JavaScript injection vectors that were not explicitly filtered or encoded
-
Review browser execution of stored commentsCreate a test comment containing a benign payload (such as <img src=x onerror=alert(1)>) using a test account, then view that comment from a different browser session to confirm script execution occursAffected if The payload executes JavaScript in the viewing browser, confirming the XSS vulnerability is active and exploitable
Your environment is affected if you are running Synel Eharmony version 8.0.2.3, the comments feature is enabled, and stored comments can execute JavaScript in viewing users' browsers without sanitization.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement strict input validation and context-aware output encoding for the comments field, along with Content-Security-Policy headers to mitigate script execution.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-22791 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-22791 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data