CVE-2022-22518: A bug in the CODESYS V3 CmpUserMgr component fails to correctly apply a security policy.
Noroxi assessment
Priority: Monitor (action score 26/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.61% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to the record, no fixed version is available yet.
Low priority for now. Update when a fix is released; follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
A bug in CmpUserMgr component can lead to only partially applied security policies. This can result in enabled, anonymous access to components part of the applied security policy.
- Published
- Apr 7, 2022
- Updated
- Jun 17, 2026
- EPSS
- 0.6% · 49th percentile
- CWE
- CWE-276
Report tools
Action score
26
Monitor
Low priority for now.
- CVSS
- 26 / 40 · 6.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.6%
CNA vs NVD score
- NVD
- —
- CNA · CERTVDE
- 6.5
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| codesys | control for beaglebone sl | cpe:2.3:a:codesys:control_for_beaglebone_sl |
| codesys | control for beckhoff cx9020 | cpe:2.3:a:codesys:control_for_beckhoff_cx9020 |
| codesys | control for empc-a\/imx6 sl | cpe:2.3:a:codesys:control_for_empc-a\/imx6_sl |
| codesys | control for iot2000 sl | cpe:2.3:a:codesys:control_for_iot2000_sl |
| codesys | control for linux sl | cpe:2.3:a:codesys:control_for_linux_sl |
| codesys | control for pfc100 sl | cpe:2.3:a:codesys:control_for_pfc100_sl |
| codesys | control for pfc200 sl | cpe:2.3:a:codesys:control_for_pfc200_sl |
| codesys | control for raspberry pi sl | cpe:2.3:a:codesys:control_for_raspberry_pi_sl |
| codesys | control for wago touch panels 600 sl | cpe:2.3:a:codesys:control_for_wago_touch_panels_600_sl |
| codesys | control runtime system toolkit | cpe:2.3:a:codesys:control_runtime_system_toolkit |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- codesys control for beaglebone sl4.4.0.0 and later · before 4.5.0.0
- codesys control for beckhoff cx90204.4.0.0 and later · before 4.5.0.0
- codesys control for empc-a/imx6 sl4.4.0.0 and later · before 4.5.0.0
- codesys control for iot2000 sl4.4.0.0 and later · before 4.5.0.0
- codesys control for linux sl4.4.0.0 and later · before 4.5.0.0
- codesys control for pfc100 sl4.4.0.0 and later · before 4.5.0.0
- codesys control for pfc200 sl4.4.0.0 and later · before 4.5.0.0
- codesys control for raspberry pi sl4.4.0.0 and later · before 4.5.0.0
- codesys control for wago touch panels 600 sl4.4.0.0 and later · before 4.5.0.0
- codesys control runtime system toolkit3.5.17.0 and later · before 3.5.18.0
Versions reported by the vendor
Affected version ranges reported by the assigning authority (CERTVDE). Independent of NVD's CPE analysis and usually ahead of it.
CODESYS CODESYS Control for BeagleBone SL
- V4.5.0.0 and later · before V4.5.0.0affected
CODESYS CODESYS Control for Beckhoff CX9020 SL
- V4.5.0.0 and later · before V4.5.0.0affected
CODESYS CODESYS Control for emPC-A/iMX6 SL
- V4.5.0.0 and later · before V4.5.0.0affected
CODESYS CODESYS Control for IOT2000 SL
- V4.5.0.0 and later · before V4.5.0.0affected
CODESYS CODESYS Control for Linux SL
- V4.5.0.0 and later · before V4.5.0.0affected
CODESYS CODESYS Control for PFC100 SL
- V4.5.0.0 and later · before V4.5.0.0affected
CODESYS CODESYS Control for PFC200 SL
- V4.5.0.0 and later · before V4.5.0.0affected
CODESYS CODESYS Control for Raspberry Pi SL
- V4.5.0.0 and later · before V4.5.0.0affected
CODESYS CODESYS Control for WAGO Touch Panels 600 SL
- V4.5.0.0 and later · before V4.5.0.0affected
CODESYS CODESYS Control Runtime System Toolkit
- V3.5.18.0 and later · before V3.5.18.0affected
Same product
codesys: all recordsOther highest-scoring records for the same primary product.
- CVE-2019-9010An issue was discovered in 3S-Smart CODESYS V3 products.40Plan
- CVE-2018-10612In 3S-Smart Software Solutions GmbH CODESYS Control V3 products prior to version 3.5.14.0, user access management and communication encrypti39Monitor
- CVE-2022-47379CODESYS: Multiple products prone to out-of-bounds write36Monitor
Published before and after this one in the same product
- ← EarlierCVE-2022-22515Apr 7, 2022 · A component of the CODESYS Control runtime system allows read and write access to configuration files32Monitor
- ← EarlierCVE-2022-22517Apr 7, 2022 · Communication Components in multiple CODESYS products vulnerable to communication channel disruption30Monitor
- Later →CVE-2022-22519Apr 7, 2022 · Special HTTP(s) Requests can cause a buffer-read causing a crash of the webserver and the runtime system.31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- low · data can be read
- Integrity
- low · data or configuration can be modified
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- Low
- Integrity impact
- Low
- Availability impact
- None
Weakness class (CWE)
CWE-276 · Incorrect Default PermissionsCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
Change log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.