CVE-2023-6904
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 · uneditedA vulnerability classified as problematic was found in Jahastech NxFilter 4.3.2.5. This vulnerability affects unknown code of the file /config,admin.jsp. The manipulation of the argument admin_name leads to cross-site request forgery. The attack can be initiated remotely. VDB-248266 is the identifier assigned to this vulnerability. NOTE: The vendor was contacted early about this disclosure but did not respond in any way.
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 CSRF vulnerability exists in Jahastech NxFilter 4.3.2.5 within the /config,admin.jsp endpoint. The admin_name parameter lacks proper anti-CSRF protection, allowing remote attackers to trick authenticated administrators into performing unintended administrative actions by luring them to malicious web pages.
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= 4.3.2.5CVSS 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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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.
-
Confirm NxFilter versionAccess the admin interface and check the version information typically displayed in the admin dashboard or system settings, or inspect the application banner if exposed via HTTP headersAffected if The installed version is exactly 4.3.2.5
-
Verify admin interface is accessibleAttempt to access the /config,admin.jsp endpoint over HTTP/HTTPS to confirm the application is running and the admin panel is reachableAffected if The /config,admin.jsp endpoint responds and exposes admin functionality
-
Check for anti-CSRF token presenceSubmit a request to /config,admin.jsp and examine the response HTML for the presence of a synchronizer token, anti-CSRF token, or hidden form field containing a unique token valueAffected if No anti-CSRF token is found in the admin form submission page
-
Inspect session cookie attributesExamine the session cookies returned by the application using browser developer tools or curl -I, looking for SameSite and Secure attributesAffected if Session cookies lack SameSite=Strict or SameSite=Lax attributes
-
Verify Origin/Referer header validationSubmit a request to /config,admin.jsp with a mismatched or missing Origin/Referer header and observe whether the request is rejectedAffected if The application accepts requests without validating Origin or Referer headers
A user is affected if they are running NxFilter version 4.3.2.5 and the admin interface lacks anti-CSRF tokens on the /config,admin.jsp endpoint.
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 synchronizer token pattern (anti-CSRF tokens) on all state-changing admin operations and validate Origin/Referer headers. Also set SameSite=Strict or SameSite=Lax on session cookies.
- Consultation3.0 h
- Implementation10.0 h
- Testing5.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,904.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-6904 — 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-2023-6904 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