dbcve.org
Website Article MonetizationWordPress extension · Magenet

CVE-2024-1379

MEDIUM · 6.1 CVSS v3.1 Published 2024-03-20
Fix available
A fix is available. Upgrade to 1.0.12 or later.
See remediation →
68/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 Website Article Monetization By MageNet plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'abp_auth_key' parameter in all versions up to, and including, 1.0.11 due to insufficient input sanitization and output escaping and a missing authorization check. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

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 Website Article Monetization By MageNet WordPress plugin versions up to 1.0.11 have a stored XSS vulnerability in the 'abp_auth_key' parameter. Unauthenticated attackers can inject arbitrary JavaScript due to missing input sanitization, output escaping, and authorization checks. The malicious script executes whenever users access affected pages.

MitigationUpdate the MageNet plugin to version 1.0.12 or later, which contains the security patch addressing the input sanitization, output escaping, and authorization issues.

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
Website Article MonetizationWordPress extension
Affected:< 1.0.12

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

CVSS:3.1/AV:N/AC:L/PR:N/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 Magenet plugin installation and version
    Access WordPress admin dashboard, go to Plugins > Installed Plugins, locate 'Magenet Website Article Monetization' or similar Magenet plugin, and note the version number displayed.
    Affected if The plugin is installed and the version shown is below 1.0.12 (such as 1.0.11, 1.0.10, etc.).
  2. Check plugin directory for version file
    Navigate to wp-content/plugins/ directory (or folder named similarly like magenet-monetization), locate the main plugin PHP file or readme.txt, and inspect the version declared within.
    Affected if The version declared in the plugin files is 1.0.11 or lower.
  3. Identify the abp_auth_key setting location
    Access the WordPress plugin settings page for Magenet (usually under Settings or a dedicated Magenet menu item), locate the field labeled 'abp_auth_key' or 'Auth Key' where the authorization key can be configured.
    Affected if The abp_auth_key configuration field exists and is visible, indicating the vulnerable setting is present.
  4. Confirm unauthenticated access exposure
    Attempt to access the plugin settings page URL directly without logging into WordPress admin, or check if the plugin registers any REST API endpoints or public-facing forms that accept the abp_auth_key parameter.
    Affected if The settings interface or related endpoints are accessible without authentication, confirming the lack of authorization checks described in the CVE.

A user is affected if the Magenet Website Article Monetization plugin is installed with a version lower than 1.0.12 and the abp_auth_key configuration field is present and exposed (particularly to unauthenticated access).

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 1.0.12 or later
Fixed in 1.0.12
Interim mitigation

Update the MageNet plugin to version 1.0.12 or later, which contains the security patch addressing the input sanitization, output escaping, and authorization issues.

Recommended fix High confidence

1.0.12

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate 'Website Article Monetization By MageNet' in the plugin list
  4. If an update is available, click 'Update now' to install version 1.0.12 or later
  5. Alternatively, manually download version 1.0.12 or higher from the WordPress plugin repository and upload via Plugins > Add New > Upload Plugin

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

Fix this in Website Article Monetization Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
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,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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