CVE-2023-41086
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 · uneditedCross-site request forgery (CSRF) vulnerability exists in FURUNO SYSTEMS wireless LAN access point devices. If a user views a malicious page while logged in, unintended operations may be performed. Affected products and versions are as follows: ACERA 1210 firmware ver.02.36 and earlier, ACERA 1150i firmware ver.01.35 and earlier, ACERA 1150w firmware ver.01.35 and earlier, ACERA 1110 firmware ver.01.76 and earlier, ACERA 1020 firmware ver.01.86 and earlier, ACERA 1010 firmware ver.01.86 and earlier, ACERA 950 firmware ver.01.60 and earlier, ACERA 850F firmware ver.01.60 and earlier, ACERA 900 firmware ver.02.54 and earlier, ACERA 850M firmware ver.02.06 and earlier, ACERA 810 firmware ver.03.74 and earlier, and ACERA 800ST firmware ver.07.35 and earlier. They are affected when running in ST(Standalone) mode.
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 · high confidenceCSRF vulnerability in FURUNO SYSTEMS ACERA wireless LAN access point web interfaces. When an authenticated administrator views a malicious webpage, the attacker's site can silently trigger unauthorized operations on the affected AP's admin interface by leveraging the active session, allowing configuration changes or device manipulation without the user's consent.
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<= 02.36<= 01.35<= 01.35<= 01.76<= 01.86<= 01.86<= 01.60<= 01.60CVSS 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.
-
Identify the ACERA device modelCheck the device label, web interface login page, or administrative console for the exact model number (e.g., Acera 1210, 1150i, 1110, 1020, 1010, 950, 850f)Affected if The device is any of the ACERA models listed in the affected products
-
Locate the firmware versionAccess the web administrative interface and navigate to the Status or System Information page to view the installed firmware version, or check the device documentation for CLI commands to retrieve firmware versionAffected if The firmware version cannot be determined or is at or below the affected thresholds
-
Compare firmware version against affected rangesMatch your installed firmware version to the affected thresholds: Acera 1210 <= 02.36, Acera 1150i/1150w <= 01.35, Acera 1110 <= 01.76, Acera 1020/1010 <= 01.86, Acera 950/850f <= 01.60Affected if Your firmware version is at or below the threshold for your specific model
-
Confirm the web management interface is enabledCheck if the HTTP/HTTPS web administrative interface is accessible on the device by attempting to reach the login page or checking the device network configurationAffected if The web interface is enabled and accessible on the network
You are affected if your ACERA device model and firmware version fall within the affected ranges AND the web management interface is enabled, allowing an authenticated session to be hijacked via CSRF.
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 dataUpdate firmware to versions beyond those specified (ACERA 1210: >02.36, ACERA 1150i/1150w: >01.35, ACERA 1110: >01.76, ACERA 1020/1010: >01.86, ACERA 950/850F: >01.60, ACERA 900: >02.54, ACERA 850M: >02.06, ACERA 810: >03.74, ACERA 800ST: >07.35) while operating in ST (Standalone) mode. Until patched, avoid browsing untrusted sites while logged into the AP admin interface.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-41086 — 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-41086 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