Skip to content
Noroxi
CVE-2024-6853· NVD / CVE Program· CNA WPScan

WP MultiTasking <= 0.1.12 - Welcome Popup Update via CSRF

The WP MultiTasking WordPress plugin through 0.1.12 does not have CSRF check when updating welcome popups, which could allow attackers to make logged admins perform such action via a CSRF attack

MediumCVSS 4.3 · v3.1—No exploit No fix recorded
Published
Sep 8, 2024
Updated
Jun 17, 2026
EPSS
0.2% · 12th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

17

Monitor

Low priority for now.

CVSS
17 / 40 · 4.3 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

CISA SSVC decision

Exploitation
proof of concept
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Affected systems

VendorProduct
ngothangwp multitasking

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • ngothang wp multitaskingup to 0.1.12 inclusive

Versions reported by the vendor

Affected version ranges reported by the assigning authority (WPScan). Independent of NVD's CPE analysis and usually ahead of it.

  • Unknown WP MultiTasking

    • up to and including 0.1.12affected · semver

Other highest-scoring records for the same primary product.

  • CVE-2024-6859WP MultiTasking <= 0.1.12 - Reflected XSS via Shortcode
    21Monitor
  • CVE-2024-8189WP MultiTasking - WP Utilities <= 0.1.17 - Authenticated (Administrator+) Stored Cross-Site Scripting
    19Monitor
  • CVE-2024-6860WP MultiTasking <= 0.1.12 - Permalink Suffix Update via CSRF
    17Monitor
  • CVE-2024-6857WP MultiTasking <= 0.1.12 - Header/Footer/Body Script Update via CSRF
    17Monitor
  • CVE-2024-6856WP MultiTasking <= 0.1.12 - SMTP Settings Update via CSRF
    17Monitor
  • CVE-2024-6855WP MultiTasking <= 0.1.12 - Exit Popup Update via CSRF
    17Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

No fix version is recorded for this entry. Check the references for vendor advisories.

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2024-68520 days apartWP MultiTasking <= 0.1.12 - Settings Update via CSRF
    17Monitor
  • CVE-2024-68550 days apartWP MultiTasking <= 0.1.12 - Exit Popup Update via CSRF
    17Monitor
  • CVE-2024-68560 days apartWP MultiTasking <= 0.1.12 - SMTP Settings Update via CSRF
    17Monitor
  • CVE-2024-6857213 days apartWP MultiTasking <= 0.1.12 - Header/Footer/Body Script Update via CSRF
    17Monitor
  • CVE-2024-6860213 days apartWP MultiTasking <= 0.1.12 - Permalink Suffix Update via CSRF
    17Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • A user must open a link or visit a page.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
low · data or configuration can be modified
Availability
none
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality impact
None
Integrity impact
Low
Availability impact
None

CVSS vector

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

nvd-primary

Root cause

State-changing requests rely on the session cookie the browser sends automatically; nothing verifies that the request came from the user’s own page.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

ts
app.use(session({ cookie: { httpOnly: true } }));app.post("/account/address", updateAddress);

Fixed

ts
app.use(session({ cookie: { httpOnly: true, sameSite: "lax" } }));app.post("/account/address", csrfProtection, updateAddress);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Change log

No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.

All records