CyberSecBulletin
CVE-2022-3154NVD status: Modified

Woo Billingo Plus: Cross-Site Request Forgery

CVE-2022-3154 is a high-severity cross-site request forgery vulnerability in Woo Billingo Plus from TODO, with a CVSS 3.1 base score of 7.1 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. The record lists version 4.4.5.4 as the first without the flaw, so updating Woo Billingo Plus to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.41% chance of exploitation within 30 days, which is low compared with other CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update Woo Billingo Plus to 4.4.5.4 or a later version.
  2. Update Integration for Billingo & Gravity Forms to 1.0.4 or a later version.
  3. Update Integration for Szamlazz.hu & Gravity Forms to 1.2.7 or a later version.
  4. Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
  5. 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

VendorProductAffected versionsFixed in
TODOWoo Billingo Plus4.4.5.4 up to, but not including, 4.4.5.44.4.5.4
TODOIntegration for Billingo & Gravity Forms1.0.4 up to, but not including, 1.0.41.0.4
TODOIntegration for Szamlazz.hu & Gravity Forms1.2.7 up to, but not including, 1.2.71.2.7

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
NoneNo data is disclosed.
Integrity
HighData or code can be modified at will.
Availability
LowPerformance or availability is reduced.

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:L. Scored by NVD.

Official description

The Woo Billingo Plus WordPress plugin before 4.4.5.4, Integration for Billingo & Gravity Forms WordPress plugin before 1.0.4, Integration for Szamlazz.hu & Gravity Forms WordPress plugin before 1.2.7 are lacking CSRF checks in various AJAX actions, which could allow attackers to make logged in Shop Managers and above perform unwanted actions, such as deactivate the plugin's license

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).

More Cross-Site Request Forgery vulnerabilities (CWE-352)

Timeline

  1. CVE record published.
  2. Record last changed materially (score, affected products, status or references).

References

Technical write-ups (may include proof of concept)

Recent Cross-Site Request Forgery vulnerabilities

Spotted an error? Tell us.