dbcve.org
Acera 1210 FirmwareOperating system · Furunosystems

CVE-2023-39429

MEDIUM · 5.4 CVSS v3.1 Published 2023-10-03
Fix available
A fix is available. Upgrade to after 02.36 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 · unedited
Cross-site scripting vulnerability in FURUNO SYSTEMS wireless LAN access point devices allows an authenticated user to inject an arbitrary script via a crafted configuration. 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 confidence

Cross-site scripting (XSS) vulnerability in FURUNO SYSTEMS ACERA wireless LAN access point devices allows an authenticated attacker to inject arbitrary JavaScript or HTML into the web management interface via a crafted configuration file. The vulnerability exists only when devices operate in ST (Standalone) mode and affects multiple ACERA models with firmware versions prior to the fixes.

MitigationApply vendor-supplied firmware updates to all affected ACERA devices running in ST mode; until updates are available, restrict administrative access to trusted users only to limit the attack surface.

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
Acera 1210 FirmwareOperating system
Affected:<= 02.36
Acera 1150i FirmwareOperating system
Affected:<= 01.35
Acera 1150w FirmwareOperating system
Affected:<= 01.35
Acera 1110 FirmwareOperating system
Affected:<= 01.76
Acera 1020 FirmwareOperating system
Affected:<= 01.86
Acera 1010 FirmwareOperating system
Affected:<= 01.86
Acera 950 FirmwareOperating system
Affected:<= 01.60
Acera 850f FirmwareOperating system
Affected:<= 01.60

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the ACERA model
    Locate the model number on the device label or within the web management interface device status page
    Affected if The model is not one of the following: 1210, 1150i, 1150w, 1110, 1020, 1010, 950, or 850f - these are not affected
  2. Determine the installed firmware version
    Access the web management interface and navigate to the firmware or system information section to retrieve the current firmware version number
    Affected if The firmware version is at or below the vulnerable threshold for your model (02.36 for 1210, 01.35 for 1150i/1150w, 01.76 for 1110, 01.86 for 1020/1010, or 01.60 for 950/850f)
  3. Check the device operating mode
    Locate the operational mode setting within the wireless or network configuration section of the web management interface
    Affected if The device is configured to operate in ST (Standalone) mode rather than another mode such as AP or controller-managed mode

All three conditions must be true for the device to be affected: the model must be a vulnerable ACERA variant, the firmware must be at or below the specified version limit, and the device must be operating in ST mode.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 02.36
Interim mitigation

Apply vendor-supplied firmware updates to all affected ACERA devices running in ST mode; until updates are available, restrict administrative access to trusted users only to limit the attack surface.

Fix this in Acera 1210 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-39429 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-39429 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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