dbcve.org
PaytiumWordPress extension

CVE-2024-25099

MEDIUM · 5.4 CVSS v3.1 Published 2024-03-13
Fix available
A fix is available. Upgrade to after 4.4.2 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in David de Boer Paytium: Mollie payment forms & donations allows Stored XSS.This issue affects Paytium: Mollie payment forms & donations: from n/a through 4.4.2.

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

This is a stored Cross-site Scripting (XSS) vulnerability in the Paytium WordPress plugin (Mollie payment forms & donations). The vulnerability exists through version 4.4.2 due to improper neutralization of user input during web page generation, allowing attackers to inject malicious scripts that persist and execute when other users view affected pages.

MitigationUpdate Paytium to the latest version which includes proper input sanitization and output encoding. Review all form input fields and user-generated content areas for XSS vulnerabilities.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
PaytiumWordPress extension
Affected:<= 4.4.2

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/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. Verify Paytium plugin is installed
    Log into WordPress admin panel, navigate to Plugins > Installed Plugins, and look for 'Paytium' in the list of active plugins
    Affected if Paytium plugin appears in the WordPress plugins list and is activated
  2. Check installed Paytium version
    In WordPress admin, go to Plugins > Installed Plugins, find Paytium, and read the version number displayed under the plugin name. Alternatively, check the version in the plugin header file via file manager or FTP at wp-content/plugins/paytium/paytium.php
    Affected if The installed version number is 4.4.2 or lower
  3. Identify active payment or donation forms
    In WordPress admin, look for Paytium menu items (typically under 'Paytium' or 'Forms') and list all created payment forms, donation forms, or Mollie payment forms
    Affected if Any Paytium forms exist and are published on the site
  4. Determine if forms accept user input
    Review the form configuration to identify fields that accept free-text user input, such as name fields, address fields, custom text fields, or any input where donors or users can enter custom values
    Affected if Forms contain editable input fields where users can submit custom text values
  5. Check if forms are publicly accessible
    Visit the pages or posts where Paytium forms are embedded to confirm they are publicly accessible. Check the WordPress admin to see if forms are set to publish status and not restricted to administrators only
    Affected if Forms are published and accessible to visitors on the live website

The environment is affected if Paytium plugin version 4.4.2 or lower is installed, active, and has published forms with user input fields accessible on the public website.

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.

From vendor data
Upgrade available Upgrade to a release after 4.4.2
Interim mitigation

Update Paytium to the latest version which includes proper input sanitization and output encoding. Review all form input fields and user-generated content areas for XSS vulnerabilities.

Fix this in Paytium Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-25099 — 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-25099 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