dbcve.org
The MoneytizerWordPress extension · Themoneytizer

CVE-2023-6968

MEDIUM · 5.4 CVSS v3.1 Published 2024-06-06
Fix available
A fix is available. Upgrade to 10.0.1 or later.
See remediation →
61/100
Remediation priority · Elevated
Remotely reachable No privileges

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
The The Moneytizer plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 9.6.3. This is due to missing or incorrect nonce validation on multiple AJAX functions. This makes it possible for unauthenticated attackers to to update and retrieve billing and bank details, update and reset the plugin's settings, and update languages as well as other lower-severity actions via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

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

The Moneytizer WordPress plugin is vulnerable to Cross-Site Request Forgery due to missing or incorrect nonce validation on multiple AJAX functions. This allows unauthenticated attackers to forge administrative requests that can modify billing/bank details, reset plugin settings, and alter languages by tricking site administrators into clicking malicious links.

MitigationUpdate the Moneytizer plugin to version 9.6.4 or later which implements proper nonce validation on AJAX actions. As a precautionary measure, administrators should avoid clicking untrusted links while authenticated.

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
The MoneytizerWordPress extension
Affected:< 10.0.1

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
None
User interaction
Required
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/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 Moneytizer plugin is installed
    Navigate to WordPress admin > Plugins and confirm 'The Moneytizer' or 'Moneytizer' plugin appears in the list of installed plugins.
    Affected if The Moneytizer plugin is not installed on the WordPress site.
  2. Check installed plugin version
    In Plugins list, click on the Moneytizer plugin to view its details, or open the main plugin file (e.g., wp-content/plugins/themoneytizer/index.php) and look for the 'Version' header in the plugin comment block.
    Affected if The version number displayed is less than 10.0.1 (e.g., 10.0.0, 9.6.x, or any version before 10.0.1).
  3. Confirm AJAX actions are accessible
    Check if the plugin registers AJAX hooks. Inspect the main plugin PHP file for do_action('wp_ajax_') or do_action('wp_ajax_nopriv_') calls, or use a tool to probe common AJAX endpoints like /wp-admin/admin-ajax.php with the plugin's action names.
    Affected if The plugin registers AJAX actions (such as those for saving settings, modifying bank details, or changing languages) and these endpoints respond without requiring a valid nonce.
  4. Review nonce implementation in AJAX handlers
    Examine the PHP functions handling the vulnerable AJAX actions (search for functions hooked to wp_ajax_). Look for the presence of check_ajax_referer() or wp_verify_nonce() calls at the beginning of these handler functions.
    Affected if The AJAX handler functions lack nonce verification checks and process requests without validating the request origin.

A site is affected if the Moneytizer plugin version is below 10.0.1 and the plugin is active with AJAX endpoints that do not implement nonce validation.

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
Upgrade available Upgrade to 10.0.1 or later
Fixed in 10.0.1
Interim mitigation

Update the Moneytizer plugin to version 9.6.4 or later which implements proper nonce validation on AJAX actions. As a precautionary measure, administrators should avoid clicking untrusted links while authenticated.

Recommended fix High confidence

The Moneytizer version 10.0.1

  1. 1. Backup your WordPress site database and files before making any changes.
  2. 2. Navigate to Plugins > Installed Plugins in your WordPress admin dashboard.
  3. 3. Find The Moneytizer plugin in the list.
  4. 4. If an update is available, click 'Update Now' to upgrade to version 10.0.1 or later.
  5. 5. Alternatively, download version 10.0.1 from the WordPress plugin repository and upload it manually via Plugins > Add New > Upload Plugin.
  6. 6. After updating, verify the plugin is running version 10.0.1 or newer in the plugins list.
  7. 7. Clear any caching plugins and test that the plugin functionality remains intact.

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

Fix this in The Moneytizer Scoped from the published advisory
  • Consultation1.0 h
  • Implementation0.5 h
  • Testing1.0 h
  • Review / QA0.5 h
3.0 hours of engineering $750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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