CVE-2013-0731

What it is

ajax.functions.php in the MailUp plugin before 1.3.3 for WordPress does not properly restrict access to unspecified Ajax functions, which allows remote attackers to modify plugin settings and conduct cross-site scripting (XSS) attacks by setting the wordpress_logged_in cookie. NOTE: this is due to an incomplete fix for a similar issue that was fixed in 1.3.2.

At a glance

Exploitability

Can be exploited over the network without logging in. Limited direct impact.

Exploit odds

2.6% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2013-03-22 15:55 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-16 23:49 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 2.6% in the next 30 days (EPSS).
• Severity: 5.0 MEDIUM (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2013-03-22 15:55 UTC

Last modified

2026-06-16 23:49 UTC

Exploit probability

2.6% · EPSS, next 30 days

Weakness

CWE-264

Record status

Modified

Affected

• Mailup wp-mailup ≤ 1.3.2
• Mailup wp-mailup 1.0.0
• Mailup wp-mailup 1.1.0
• Mailup wp-mailup 1.1.1
• Mailup wp-mailup 1.1.2
• Mailup wp-mailup 1.1.3
• Mailup wp-mailup 1.2
• Mailup wp-mailup 1.3

Attack profile CVSS 2.0 · 5.0

Attack vector

Network

Complexity

Low

Authentication

None

Confidentiality

None

Integrity

Partial

Availability

None

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2013-0731.md and follow it. Check whether this project is affected by CVE-2013-0731. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge