Skip to content
Noroxi
CVE-2015-1434· NVD / CVE Program· CNA mitre

Multiple SQL injection vulnerabilities in my little forum before 2.3.4 allow remote administrators to execute arbitrary SQL commands via the

Multiple SQL injection vulnerabilities in my little forum before 2.3.4 allow remote administrators to execute arbitrary SQL commands via the (1) letter parameter in a user action or (2) edit_category parameter to index.php.

MediumCVSS 6.5 · v2.0—No exploit No fix recorded
Published
Feb 16, 2015
Updated
Jun 16, 2026
EPSS
1.9% · 78th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

27

Monitor

Low priority for now.

CVSS
26 / 40 · 6.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
1 / 30 · 1.9%

Affected systems

VendorProduct
mylittleforummy little forum

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • mylittleforum my little forumup to 2.3.3 inclusive

Other highest-scoring records for the same primary product.

  • CVE-2026-25923Phar Deserialization leading to Arbitrary File Deletion in my little forum
    34Monitor
  • CVE-2010-2133SQL injection vulnerability in contact.php in My Little Forum allows remote attackers to execute arbitrary SQL commands via the id parameter
    31Monitor
  • CVE-2019-12253my little forum before 2.4.20 allows CSRF to delete posts, as demonstrated by mode=posting&delete_posting.
    26Monitor
  • CVE-2018-15569my little forum 2.4.12 allows CSRF for deletion of users.
    26Monitor
  • CVE-2018-14937The Add page option in my little forum 2.4.12 allows XSS via the Menu Link field.
    19Monitor
  • CVE-2018-14936The Add page option in my little forum 2.4.12 allows XSS via the Title field.
    19Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

No fix version is recorded for this entry. Check the references for vendor advisories.

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • No special conditions are required; it is repeatable.

If successful

Confidentiality
P · data can be read
Integrity
P · data or configuration can be modified
Availability
P · the service can be disrupted
Attack complexity
Low
Confidentiality impact
P
Integrity impact
P
Availability impact
P

CVSS vector

AV:N/AC:L/Au:S/C:P/I:P/A:P

nvd-primary

Root cause

The query text is built by concatenating user input. The database cannot tell where the data ends and the command begins.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

ts
const owner = req.query.owner;const rows = await db.query(  "SELECT * FROM files WHERE owner = '" + owner + "'");

Fixed

ts
const owner = req.query.owner;const rows = await db.query(  "SELECT * FROM files WHERE owner = $1",  [owner]);

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Change log

No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.

References

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records