LiveActive security incident?Get immediate response
CVE Record

CVE-2022-26173: JForum v2.8.0 was discovered to contain a Cross-Site Request Forgery (CSRF) via http://target_host:port/jfo...

JForum v2.8.0 was discovered to contain a Cross-Site Request Forgery (CSRF) via http://target_host:port/jforum-2.8.0/jforum.page, which allows attackers to arbitrarily add admin accounts.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2022-26173 describes a CSRF flaw in JForum v2.8.0 that could let an attacker cause an administrator’s browser to create new admin accounts. The source bundle does not provide CVSS scoring, confirmed fixes, or evidence of active exploitation.

Executive priority

Prioritize assessment if JForum v2.8.0 is in use. The business risk is unauthorized forum administration, but urgency depends on exposure and whether administrators actively use the system.

Technical view

The CVE description identifies a CSRF issue at JForum v2.8.0’s jforum.page endpoint with impact described as arbitrary admin account creation. Public references include JForum project pages and a GitHub proof-of-concept reference. No KEV listing or vendor remediation detail is provided in the bundle.

Likely exposure

Exposure is most likely limited to organizations running JForum v2.8.0, especially forums where administrators use browser sessions on reachable deployments.

Exploitation context

A public proof-of-concept reference is listed, but the bundle does not establish active exploitation. KEV is false, so treat exploitation as plausible but unconfirmed.

Researcher notes

Evidence is sparse: affected CPEs, CVSS, CWE mapping, and official patch status are absent from the bundle. Do not assume affected versions beyond JForum v2.8.0 without vendor confirmation.

Mitigation direction

  • Check JForum project and community guidance for fixed versions or workarounds.
  • Prioritize migration or upgrade planning for any confirmed JForum v2.8.0 instance.
  • Restrict administrative access to trusted networks where feasible.
  • Review and remove unauthorized administrator accounts.
  • Require administrators to avoid untrusted links while logged into JForum.

Validation and detection

  • Inventory internet-facing and internal JForum deployments and confirm exact versions.
  • Review administrator account creation history for unexpected accounts.
  • Inspect logs for suspicious requests to JForum administrative user-management paths.
  • Confirm whether admin-changing actions have CSRF protections enabled.
  • Document compensating controls until vendor guidance is confirmed.
Prepared
Confidence
medium
Sources
6

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.

cve · low confidence lookup

CVE-2022-26173 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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

0CVSS vectors
3Timeline events
1ADP providers
5Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.