dbcve.org
Export Post InfoWordPress extension · Apasionados

CVE-2022-38061

MEDIUM · 5.7 CVSS v3.1 Published 2022-09-23
Fix available
A fix is available. Upgrade to after 1.2.0 or later.
See remediation →
61/100
Remediation priority · Elevated
Remotely reachable

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
Authenticated (author+) CSV Injection vulnerability in Export Post Info plugin <= 1.2.0 at WordPress.

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

Authenticated users with author-level privileges or higher can inject malicious spreadsheet formulas (CSV injection) into post content within the Export Post Info WordPress plugin. When the plugin exports post data to CSV format, these injected formulas are included without sanitization. When the resulting CSV is opened in spreadsheet software like Excel or LibreOffice, the formulas can execute arbitrary commands or exfiltrate data.

MitigationUpdate Export Post Info plugin to version >1.2.0 which includes proper input sanitization, or implement server-side validation to escape or remove formula characters (=, +, -, @, tab, CR) from user-supplied content before CSV export.

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
Export Post InfoWordPress extension
Affected:<= 1.2.0

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
Low
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:H/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 Export Post Info plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Export Post Info' by Apasionados, or check the /wp-content/plugins/ directory for the export-post-info folder
    Affected if the plugin is present in the WordPress installation
  2. Check installed plugin version
    In Plugins page, look at the version column for Export Post Info, or open the main plugin file (export-post-info.php) and check the Version header in the plugin comments
    Affected if the version is 1.2.0 or lower
  3. Confirm CSV export feature is accessible
    Check if the plugin's export functionality is active by visiting the plugin settings page or attempting to access any export feature (usually under Posts or a dedicated Export menu)
    Affected if the export functionality is enabled and accessible to users
  4. Identify users with author-level or higher access
    In WordPress admin, go to Users > All Users and review role assignments; author, editor, and administrator roles have the privilege to create/edit posts where malicious formulas could be injected
    Affected if there are users with author, editor, or administrator roles who can create or edit post content
  5. Inspect post content for formula injection characters
    Review recent posts for unsanitized characters at the start of fields: = (equals), + (plus), - (minus), @ (at), tab, or CR characters which indicate potential CSV injection payloads
    Affected if post content contains spreadsheet formula characters without prior sanitization

A user is affected if the Export Post Info plugin version 1.2.0 or lower is installed AND the CSV export feature is active AND users with author-level or higher privileges exist in WordPress.

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 a release after 1.2.0
Interim mitigation

Update Export Post Info plugin to version >1.2.0 which includes proper input sanitization, or implement server-side validation to escape or remove formula characters (=, +, -, @, tab, CR) from user-supplied content before CSV export.

Recommended fix Moderate confidence

Latest version of Export Post Info plugin (newer than 1.2.0) from wordpress.org

  1. Navigate to WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Locate 'Export Post Info' plugin
  4. Check if update is available and install the latest version
  5. Alternatively, download the latest version from wordpress.org/plugins/export-post-info and upload via Plugins > Add New > Upload Plugin
  6. Verify the plugin is updated to a version newer than 1.2.0

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

Fix this in Export Post Info Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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