dbcve.org
Server-Side Request Forgery (SSRF)Weakness · CWE-918

CVE-2024-32803

MEDIUM · 6.4 CVSS v3.1 Published 2024-04-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
Server-Side Request Forgery (SSRF) vulnerability in 2day.Sk, Webikon SuperFaktura WooCommerce.This issue affects SuperFaktura WooCommerce: from n/a through 1.40.3.

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 · high confidence

Server-Side Request Forgery (SSRF) vulnerability in SuperFaktura WooCommerce plugin allows attackers to make the server perform requests to arbitrary URLs due to insufficient validation of user-controlled URL parameters, potentially exposing internal services and network resources.

MitigationUpdate SuperFaktura WooCommerce to the latest version beyond 1.40.3, and implement strict URL validation using allow-lists to restrict requests to permitted domains only.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS 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
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm SuperFaktura WooCommerce plugin is installed
    Navigate to WordPress admin > Plugins, or check the /wp-content/plugins/ directory for a folder named 'superfaktura' or similar
    Affected if Plugin is present in the WordPress installation
  2. Identify installed plugin version
    In WordPress admin > Plugins > SuperFaktura WooCommerce, view the plugin details to see the version number
    Affected if Version is 1.40.3 or lower (all versions up to 1.40.3 are affected)
  3. Check if plugin API functionality is enabled
    Navigate to plugin settings (usually under WooCommerce > Settings > SuperFaktura) and verify if the API integration or any URL-based feature is active
    Affected if API sync or URL-related features are enabled and accessible to users
  4. Inspect HTTP logs for outbound requests
    Review server access logs or use a web proxy to monitor requests originating from the server; look for requests to unexpected or internal URLs
    Affected if Server is making outbound requests to arbitrary URLs that were not initiated by legitimate admin actions

If SuperFaktura WooCommerce plugin is installed and the version is 1.40.3 or lower, and the plugin API or URL-based features are active, the environment is affected by this SSRF vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update SuperFaktura WooCommerce to the latest version beyond 1.40.3, and implement strict URL validation using allow-lists to restrict requests to permitted domains only.

Recommended fix Moderate confidence

Update SuperFaktura WooCommerce to version 1.40.4 or later (verify latest version in WordPress plugin repository or contact vendor)

  1. Check the WordPress admin panel for the SuperFaktura WooCommerce plugin under Plugins
  2. If an update to version 1.40.4 or higher is available, click 'Update Now' to install the patched version
  3. After updating, verify the plugin is active and functioning correctly
  4. If no update is available in the WordPress repository, contact the vendor (Webikon/SuperFaktura) directly to obtain the patched version 1.40.4 or higher

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-32803 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-32803 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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