Skip to main content
Menu
CVEs

CVE

Jiaxing Xiangtian OpenSNS unauthenticated remote code execution in share controller

Affects OpenSNS 3.2.1, where an unauthenticated code injection flaw can run arbitrary code on the server. No fixed version is named in the checked facts.

CVE-2021-48025Published Updated Summary written by a model

9.3CriticalCNA
Exploited
Proof of concept public, per CISA
Fix
No fix listed
Who is exposed
Not reported

Do first: Workaround: The checked facts name no workaround. Until a fix is confirmed, the only documented step is to avoid relying on the weibo/Share/shareBox feature, and the checked facts do not say whether that alone is sufficient.

Summary

OpenSNS 3.2.1 contains an unauthenticated code injection vulnerability in the shareBox method of ShareController that allows attackers to invoke arbitrary model methods via the query parameter. Attackers can send crafted GET requests to /index.php?s=weibo/Share/shareBox abusing parse_str and ShareModel::getInfo to reach Schedule::runSchedule and execute code through assert. Exploitation evidence was first observed by the Shadowserver Foundation on 2023-10-14.

Who should check

Teams running OpenSNS 3.2.1 (Jiaxing Xiangtian Information Technology) on a web server reachable over HTTP.

“Affecting OpenSNS 3.2.1”

vulncheck.com

cve.now Index

50Pcve.now Index 50 of 100 · methodology v3 · provisional
  • Exploitation15/40CISA rates a proof of concept as public
  • Exposure20/25No login or user action needed, CISA rates it automatable · Unknown: Advisories don't say whether default setups are affected
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity10/10CVSS 9.3, total technical impact per CISA
  • No patch5/5No patch listed yet

What would change the score

  • Would score about 80 if added to CISA KEV
  • Would score about 75 if CISA's SSVC rates exploitation active
  • Would score about 55 if advisories confirm default setups are exposed

What to do

  • Workaround: The checked facts name no workaround. Until a fix is confirmed, the only documented step is to avoid relying on the weibo/Share/shareBox feature, and the checked facts do not say whether that alone is sufficient.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2021-48025 (OpenSNS 3.2.1 Unauthenticated RCE via weibo/Share/shareBox), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2021-48025 (entry last updated 2026-11-18):
Affected:
- Jiaxing Xiangtian Information Technology OpenSNS: versions 3.2.1
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- Affects OpenSNS 3.2.1 (source: https://www.vulncheck.com/advisories/opensns-3.2.1-unauthenticated-rce-via-weibo-share-sharebox)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2021-48025 is not listed as of cve.now's last read.
This KEV status is for CVE-2021-48025 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/projectdiscovery/nuclei-templates/blob/main/http/vulnerabilities/other/opensns-rce.yaml
- https://www.vulncheck.com/advisories/opensns-3.2.1-unauthenticated-rce-via-weibo-share-sharebox
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2021-48025
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2021-48025"}.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: poc · Automatable: yes · Technical impact: total

  4. Record last updated

Affected versions

  • Jiaxing Xiangtian Information Technology OpenSNS

    3.2.1

Evidence 5

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2021-48025

Is CVE-2021-48025 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked.Source: cve.now feed data

What does this mean?

The weibo/Share/shareBox component of OpenSNS 3.2.1 contains an unauthenticated code injection flaw. The checked facts say it lets an attacker without a login execute code on the server through assert.Source: vulncheck.com

Which versions are affected by CVE-2021-48025?

OpenSNS: version 3.2.1.Source: cve.now feed data

Am I affected, and how do I check?

The checked facts list OpenSNS 3.2.1 as the affected version, with no version range given. To check a installation, look at the OpenSNS version information in the product's admin or configuration pages.Source: vulncheck.com

How do I fix CVE-2021-48025?

The checked facts name no fixed version and no vendor patch identifiers. Check the vendor's channels for an update before relying on any version.Source: vulncheck.com

What if there's no patch?

The checked facts name no workaround. Until a fix is confirmed, the only documented step is to avoid relying on the weibo/Share/shareBox feature, and the checked facts do not say whether that alone is sufficient.Source: vulncheck.com

More CVEs