Republish Old PostsWordPress extension · Mariosalexandrou
CVE-2023-52145
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 Marios Alexandrou Republish Old Posts.This issue affects Republish Old Posts: from n/a through 1.21.
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 confidenceCross-Site Request Forgery (CSRF) vulnerability in the Republish Old Posts WordPress plugin allows attackers to trick authenticated administrators into performing unintended actions such as republishing old posts without proper nonce validation. The lack of anti-CSRF tokens on state-changing operations enables malicious requests to be executed when a logged-in administrator visits a crafted page.
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
Republish Old PostsWordPress extension
<= 1.21CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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 plugin installationCheck if the Republish Old Posts plugin exists in your WordPress installation at wp-content/plugins/ directory or via WP Admin > PluginsAffected if Plugin is present in the installation
-
Identify installed versionOpen the main plugin file (republish-old-posts.php) and locate the version header comment, or check via WP Admin > Plugins > Republish Old PostsAffected if Version is 1.21 or lower (any version <= 1.21)
-
Inspect action handlers for nonce validationExamine the plugin PHP files for state-changing functions (actions handling post republishing) and search for wp_verify_nonce, check_admin_referer, or nonce verification callsAffected if No nonce verification is found in the republishing action handlers
-
Verify admin action accessibilityCheck if the plugin registers admin menu pages or AJAX handlers that perform state changes without requiring nonce tokens in the requestAffected if State-changing admin actions accept requests without anti-CSRF token validation
If the Republish Old Posts plugin version 1.21 or lower is installed and the plugin code lacks nonce validation on its republishing actions, the environment is vulnerable to CVE-2023-52145.
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 · scopedImplement anti-CSRF tokens (nonce validation) on all state-changing operations within the plugin, particularly the post republishing functionality. Until a patch is available, consider disabling the plugin or adding server-side request origin validation.
Update to plugin version 1.22 or later (check WordPress plugin repository for the latest available version)
- 1. Navigate to the WordPress admin dashboard
- 2. Go to Plugins > Installed Plugins
- 3. Locate the 'Republish Old Posts' plugin
- 4. If an update is available, click 'Update Now'
- 5. Verify the updated version is 1.22 or higher
- 6. Test the plugin functionality to ensure the update didn't break existing features
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Republish Old Posts
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-52145 — 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-2023-52145 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