Auto Upload ImagesWordPress extension · Auto Upload Images Project
CVE-2022-42880
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in Ali Irani Auto Upload Images plugin <= 3.3 versions allows Stored Cross-Site Scripting (XSS).
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 Ali Irani Auto Upload Images WordPress plugin (versions <= 3.3) has a CSRF vulnerability that can be chained to achieve Stored XSS. An attacker can trick a logged-in administrator into submitting a crafted request that stores malicious JavaScript in the plugin's settings or upload functionality, which then executes when other users view the affected content.
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
Auto Upload ImagesWordPress extension
< 3.3.1CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm plugin installation and versionNavigate to WordPress admin > Plugins and locate 'Auto Upload Images' in the list. Check the version number displayed below the plugin name.Affected if The installed version is 3.3 or lower (versions prior to 3.3.1)
-
Check plugin settings for stored XSS payloadsGo to the plugin's settings page (usually under Settings > Auto Upload Images). Inspect the input fields and text areas for any unexpected script tags, iframe tags, or javascript: URLs that you did not intentionally add.Affected if The plugin settings contain suspicious HTML or JavaScript content such as <script>, <img onerror>, or event handlers like onload/onerror
-
Inspect plugin-generated content for XSSView a post, page, or media library item that the plugin has modified. Use browser developer tools to inspect the HTML source and look for unescaped user-supplied content in attributes or text nodes.Affected if Content rendered by the plugin contains raw, unescaped HTML or JavaScript that could execute
-
Verify nonce protection on plugin formsUse browser developer tools to view the page source of the plugin's admin settings page. Check if forms contain a hidden input field with a nonce value (wpnonce or similar) and if the plugin validates it on submission.Affected if Forms and AJAX actions in the plugin lack nonce verification fields or the nonce validation is missing in the code
-
Review access logs for CSRF patternsCheck server access logs or WordPress audit logs for POST requests to the plugin's admin-ajax.php or settings pages that lack a valid referer or origin header, which could indicate CSRF exploitation attempts.Affected if Requests to plugin endpoints are being made without proper anti-CSRF protections in place
You are affected if the Auto Upload Images plugin version is 3.3 or lower AND either the plugin settings contain suspicious stored content, forms lack nonce protection, or plugin-generated content renders unescaped HTML.
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.
dbcve · scoped3.3.1
Update the plugin to a patched version if available. Implement anti-CSRF tokens (nonces) on all state-changing forms and actions, and apply proper input validation and output escaping to prevent XSS.
Auto Upload Images version 3.3.1 or later
- Update the Auto Upload Images plugin to version 3.3.1 or the latest available version
- After updating, verify the plugin functions correctly on the site
- Test that the stored XSS vulnerability is no longer exploitable via CSRF requests
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Auto Upload Images
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,848.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-42880 — 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-2022-42880 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