dbcve.org
Auto Refresh Single PageWordPress extension · Rymera

CVE-2024-1731

HIGH · 8.8 CVSS v3.1 Published 2024-03-05
Fix available
A fix is available. Upgrade to after 1.1 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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
The Auto Refresh Single Page plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 1.1 via deserialization of untrusted input from the arsp_options post meta option. This makes it possible for authenticated attackers, with contributor-level access and above, to inject a PHP Object. No known POP chain is present in the vulnerable plugin. If a POP chain is present via an additional plugin or theme installed on the target system, it could allow the attacker to delete arbitrary files, retrieve sensitive data, or execute code.

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

The Auto Refresh Single Page WordPress plugin (versions up to 1.1) is vulnerable to PHP Object Injection via deserialization of untrusted input stored in the arsp_options post meta. Authenticated users with contributor-level access or higher can inject arbitrary PHP objects. While the plugin itself lacks a POP chain, additional plugins or themes on the target system could provide one, enabling file deletion, data exfiltration, or code execution.

MitigationUpdate the Auto Refresh Single Page plugin to a version beyond 1.1 and audit installed plugins/themes for potential POP chains that could be chained with this deserialization vulnerability.

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 Refresh Single PageWordPress extension
Affected:<= 1.1

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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if the Auto Refresh Single Page plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Auto Refresh Single Page' by Rymera, or check the plugin files in wp-content/plugins/auto-refresh-single-page/ for the main PHP file to read the version header
    Affected if The plugin is installed and its version is 1.1 or lower
  2. Verify the installed plugin version
    Open the main plugin file (usually auto-refresh-single-page.php) and locate the Version header in the plugin comment block, or check the version listed in the WordPress plugins admin page
    Affected if The version is 1.1 or any version number up to and including 1.1
  3. Check for arsp_options post meta in the database
    Query the wp_postmeta table for meta_key 'arsp_options' using: SELECT * FROM wp_postmeta WHERE meta_key = 'arsp_options'; Or use a WordPress database inspection tool
    Affected if Records with meta_key 'arsp_options' exist in the database, indicating serialized data is stored as post meta
  4. Determine if contributor-level or higher users exist
    Check WordPress user roles in Users > All Users or query wp_usermeta for wp_capabilities to identify users with contributor, author, editor, or administrator roles
    Affected if Any user account with contributor-level access or higher exists on the site

You are affected if the Auto Refresh Single Page plugin version 1.1 or lower is installed AND contributor-level or higher users exist on the site AND arsp_options post meta data is present, as these conditions enable the PHP Object Injection vulnerability.

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.

From vendor data
Upgrade available Upgrade to a release after 1.1
Interim mitigation

Update the Auto Refresh Single Page plugin to a version beyond 1.1 and audit installed plugins/themes for potential POP chains that could be chained with this deserialization vulnerability.

Fix this in Auto Refresh Single Page Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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