Integration for Szamlazz.hu & WooCommerce…: Cross-Site Request Forgery
CVE-2022-41685 is a high-severity cross-site request forgery vulnerability in Integration for Szamlazz.hu & WooCommerce (WordPress plugin) from Viszt Péter, with a CVSS 3.1 base score of 8.8 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, but only if a user takes part, for example by opening a link or file. Affected Integration for Szamlazz.hu & WooCommerce (WordPress plugin) versions: <= 5.6.3.2 through 5.6.3.2. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.45% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Integration For Szamlazz.hu & Woocommerce to 5.6.3.3 or a later version.
- Update Package Points And Shipping Labels For Woocommerce to 1.9.0.3 or a later version.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
- Because the attack needs a user to take part, warn users about unexpected links and files related to this product until it is patched.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Viszt Péter | Integration for Szamlazz.hu & WooCommerce (WordPress plugin) | <= 5.6.3.2 through 5.6.3.2 | Not stated |
| Viszt Péter | Csomagpontok és szállítási címkék WooCommerce-hez (WordPress plugin) | <= 1.9.0.2 through 1.9.0.2 | Not stated |
| Visztpeter | Integration For Szamlazz.hu & Woocommerce | before 5.6.3.3 | 5.6.3.3 |
| Visztpeter | Package Points And Shipping Labels For Woocommerce | before 1.9.0.3 | 1.9.0.3 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- RequiredA user must take an action such as opening a file or link.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 5.4 | Medium | CNA (patchstack.com) |
| CVSS 3.1 | 8.8 | High | NVD |
Official description
Multiple Cross-Site Request Forgery (CSRF) vulnerabilities in Viszt Péter's Integration for Szamlazz.hu & WooCommerce plugin <= 5.6.3.2 and Csomagpontok és szállítási címkék WooCommerce-hez plugin <= 1.9.0.2 on WordPress.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Cross-Site Request Forgery
The web application does not, or cannot, sufficiently verify whether a request was intentionally provided by the user who sent the request, which could have originated from an unauthorized actor.
How developers prevent this class of flaw
- Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, use anti-CSRF packages such as the OWASP CSRFGuard. Another example is the ESAPI Session Management control, which includes a component for CSRF.
- Ensure that the application is free of cross-site scripting issues (CWE-79), because most CSRF defenses can be bypassed using attacker-controlled script.
- Generate a unique nonce for each form, place the nonce into the form, and verify the nonce upon receipt of the form. Be sure that the nonce is not predictable (CWE-330).
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Patches and release notes
- wordpress.org/plugins/hungarian-pickup-points-for-woocommerce/#developersRelease Notes, Third Party Advisory
- wordpress.org/plugins/integration-for-szamlazzhu-woocommerce/#developersRelease Notes, Third Party Advisory
Third-party and government advisories
Recent Cross-Site Request Forgery vulnerabilities
- 8.8 High severity
- 8.8 High severity
- 8.8 High severity
- 8.8 High severity
- 8.8 High severity
- 8.8 High severity
Spotted an error? Tell us.