CVE-2026-15270
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 weakness has been identified in D-link DIR-823G 1.0.2B05_20181207. Affected by this vulnerability is an unknown functionality of the file /etc/boa/boa.conf of the component Web Interface. Executing a manipulation can lead to least privilege violation. The attack can be launched remotely. The attack requires a high level of complexity. The exploitation appears to be difficult. The exploit has been made available to the public and could be used for attacks.
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 vulnerability in the D-link DIR-823G router firmware (1.0.2B05) allows manipulation of the boa web server configuration file (/etc/boa/boa.conf) through the web interface, leading to least privilege violation where an attacker can potentially gain elevated privileges or access beyond intended permissions.
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= 1.0.2b05_20181207CVSS 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
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/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.
-
Check router firmware versionLog into the D-Link DIR-823G web admin interface (typically at 192.168.0.1) and navigate to Status or System section to view the firmware version. Alternatively, check the device label or firmware file name if you have physical access.Affected if Firmware version displayed as 1.0.2B05 or 1.0.2b05_20181207
-
Verify boa web server configuration file existsIf you have shell/telnet access to the router, navigate to /etc/boa/ and check if boa.conf file exists: ls -la /etc/boa/boa.confAffected if The file /etc/boa/boa.conf exists on the device (vulnerability requires this file to be present and modifiable)
-
Check if web interface is exposed to untrusted networksDetermine if the router's HTTP/HTTPS management interface (port 80/443) is accessible from external networks or the WAN interface. Use external port scanning or check router firewall settings.Affected if The router web interface is accessible from outside the local network or untrusted VLANs
-
Inspect boa.conf for unauthorized modificationsIf you have access to a known-good backup of boa.conf or shell access, compare the current /etc/boa/boa.conf with expected configuration. Look for unexpected script handlers, CGI paths, or privilege settings.Affected if boa.conf contains unexpected configuration changes such as modified script aliases, new CGI handlers, or altered access controls
You are affected if your D-Link DIR-823G runs firmware version 1.0.2B05 and the boa.conf file is accessible or modifiable through the web interface.
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 dataCheck D-Link support for firmware updates; if unavailable, implement network segmentation to isolate the device or consider replacing the end-of-life device.
- Consultation6.0 h
- Implementation4.0 h
- Testing3.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 $4,368.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-15270 — 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-2026-15270 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