Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2010-5317: Multiple SQL injection vulnerabilities in index.php in SweetRice CMS before 0.6.7.1 allow remote attackers to

48
This month
HIGH 7.5DOWNGRADE

CVE-2010-5317 is a high-severity flaw (CVSS 7.5) affecting sweetrice. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Multiple SQL injection vulnerabilities in index.php in SweetRice CMS before 0.6.7.1 allow remote attackers to execute arbitrary SQL commands via (1) the file_name parameter in an attachment action, (2) the post parameter in a show_comment action, (3) the sys-name parameter in an rssfeed action, or (4) the sys-name parameter in a view action.

Why this priority

  • High severity
  • Public exploit reference

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score7.5 (High)
EPSS exploit chance1.2% (top 32%)
CISA exploited listNo
WeaknessCWE-89
Published2015-01-03
Last modified2026-06-16
Publisher (CNA): MITRE · Vendor: basic-cms

Share: LinkedIn · X · Reddit

Last updated 2026-06-16 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

basic-cms sweetrice DOWNGRADE
Affected: 0.6.7.1
Fixed in: no fixed release known
Safe to downgrade to: a release before 0.6.7.1
1. Check installed version
apt-cache policy sweetrice || rpm -q sweetrice || sweetrice --version
2. No fixed release: DOWNGRADE to a release before 0.6.7.1 (Debian / Ubuntu)
apt-cache madison sweetrice sudo apt install sweetrice=<VERSION_BEFORE_0.6.7.1> sudo apt-mark hold sweetrice
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list sweetrice sudo dnf downgrade sweetrice-<VERSION_BEFORE_0.6.7.1> sudo dnf versionlock add sweetrice
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.

Public exploits and detection

Public code exists for this CVE. Treat unpatched systems as at risk, and only run PoCs in a lab.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2010-5317?

sweetrice: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2010-5317 being exploited?

CVE-2010-5317 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2010-5317 affect?

CVE-2010-5317 affects sweetrice. Severity is high (CVSS 7.5). Multiple SQL injection vulnerabilities in index.php in SweetRice CMS before 0.6.7.1 allow remote attackers to execute arbitrary SQL commands via (1) the file_name parameter in an attachment action, (2) the post parameter in a show_comment a

How urgent is CVE-2010-5317?

Priority 48/100. High severity; Public exploit reference

Software pages

PHP vulnerabilities

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.