Wp Ultimate Email Marketer PluginWordPress extension · Smackcoders
CVE-2013-3264
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 · uneditedThe WP Ultimate Email Marketer plugin 1.1.0 and possibly earlier for Wordpress does not properly restrict access to (1) list/edit.php and (2) campaign/editCampaign.php, which allows remote attackers to modify list or campaign data.
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 · moderate confidenceThe WP Ultimate Email Marketer plugin 1.1.0 for WordPress lacks proper authorization checks on list/edit.php and campaign/editCampaign.php, allowing remote attackers to modify email marketing lists and campaign data without authentication.
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
Wp Ultimate Email Marketer PluginWordPress extension
<= 1.1.0= 1.0.0= 1.0.1= 1.0.2= 1.0.3CVSS 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
- Authentication
- None
- Confidentiality
- None
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:N/I:P/A:P
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 checksWork through these to decide whether this CVE applies to you.
-
Verify the plugin is installedCheck if the WP Ultimate Email Marketer plugin exists in your WordPress plugins directory under wp-content/plugins/Affected if The plugin folder exists in the plugins directory
-
Identify the installed versionOpen the main plugin file (typically wp-content/plugins/wp-ultimate-email-marketer/plugin.php or similar) and locate the version declaration in the file header commentAffected if The version is 1.1.0 or lower, or matches 1.0.0 through 1.0.3
-
Locate the vulnerable filesCheck for the existence of list/edit.php and campaign/editCampaign.php files within the plugin directoryAffected if Both files exist in the plugin folder
-
Verify missing authorization on list/edit.phpInspect the list/edit.php file for current_user_can checks or nonce verification at the file beginningAffected if No capability check (current_user_can) and no nonce verification is present near the top of the file
-
Verify missing authorization on campaign/editCampaign.phpInspect the campaign/editCampaign.php file for current_user_can checks or nonce verification at the file beginningAffected if No capability check (current_user_can) and no nonce verification is present near the top of the file
A user is affected if the plugin version is 1.1.0 or lower and the vulnerable PHP files exist without authorization checks.
Generated from the published advisory. Verify against your own configuration.
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 dataUpdate the plugin to a patched version if available; otherwise, remove the plugin. The fix requires adding WordPress capability checks (current_user_can) and nonce verification to both affected PHP files to enforce proper access control.
Fix this in Wp Ultimate Email Marketer Plugin
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,032.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-3264 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2013-3264 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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