How severe is CVE-2022-28955?

CVE-2022-28955 has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2022-28955?

Affected package information for CVE-2022-28955 is not yet fully mapped. Check the official advisory links for details.

How do I fix CVE-2022-28955?

No fixed version has been published for CVE-2022-28955 yet. Monitor the advisory for updates, apply mitigations recommended by the vendor, and use O3 Security to track when a fix becomes available in your stack.

Is CVE-2022-28955 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2022-28955, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2022-28955?

CVE-2022-28955 has an EPSS (Exploit Prediction Scoring System) score of 92.1%, placing it in the 100th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

What type of vulnerability is CVE-2022-28955?

CVE-2022-28955 is classified as Improper Authentication (CWE-287). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

Which products and versions are affected by CVE-2022-28955?

CVE-2022-28955 affects dlink dir-816l firmware (1 version, e.g. 206b01). Check the affected-products list on this page against your deployed version to confirm exposure.

Is there exploit tooling available for CVE-2022-28955?

A Nuclei detection template exists for CVE-2022-28955, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was CVE-2022-28955 published, and has it been updated?

CVE-2022-28955 was published on May 18, 2022 and was last updated on November 21, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CVE-2022-28955

HIGH

An access control issue in D-Link DIR816L_FW206b01 allows unauthenticated attackers to access folders folder_view.php and category_view.php.

Published

May 18, 2022

Updated

Nov 21, 2024

Affected

0 pkgs

Patched

None yet

Exploits

1 known

EPSS Exploitation Probability

via FIRST.org ↗

92.1%probability of exploitation in next 30 days

Very High Risk100th percentile-0.65%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Description

An access control issue in D-Link DIR816L_FW206b01 allows unauthenticated attackers to access folders folder_view.php and category_view.php.

Affected Products

1 product · 1 configurations

dir-816l firmwaredlink

1 version

206b01

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

An access control issue in D-Link DIR816L_FW206b01 allows unauthenticate…

github.comNVDMay 2022

Frequently Asked Questions

An access control issue in D-Link DIR816L_FW206b01 allows unauthenticated attackers to access folders folder_view.php and category_view.php.

O3 Security · Impact-Aware SCA

Is CVE-2022-28955 in your stack?

O3 detects CVE-2022-28955 across dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my stack How O3 SCA works